All scored servers

Arthur Online MCP by usefulapi: tool descriptions scored io.usefulapi/arthur-online

tools/list taken
(UTC)
Connected to
https://arthur-online.usefulapi.io/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how Arthur Online MCP by usefulapi (io.usefulapi/arthur-online)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/io.usefulapi/arthur-online
Average score
51.0 / 100Cloudy
Tools
20
Near-identical descriptions
0

Across the server

No server-wide issues.

Tools

arthur_get_certificate

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_get_property

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_get_task

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_get_tenancy

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_get_tenant

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_get_unit

44 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_get_workorder

47 / 100Cloudy

Purpose
14 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_create_unit_task

49 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
12 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: description, task_type, tags, assigned_managers, emergency, private, api_notes.param_no_description
  • Minor
    The meaning of the boolean argument emergency is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument private is unclear.vague_boolean
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: unit_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_add_task_note

50 / 100Cloudy

Purpose
20 / 20
When to use
10 / 20
Arguments
13 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: content, tags.param_no_description
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: task_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_list_workorders

51 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
12 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: _q, ref, status, title, contractor, emergency, quote_required.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument emergency is unclear.vague_boolean
  • Minor
    The meaning of the boolean argument quote_required is unclear.vague_boolean

arthur_get_invoice

52 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_get_transaction

52 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
0 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Says nothing about what it returns.no_return_info
  • Minor
    Required identifiers whose description does not say where the value comes from: id. Name the tool or the place that returns it, or models look it up first.id_source_missing

arthur_list_properties

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: _q, full_address, city, postcode, property_type, unit_status.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

arthur_list_units

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
13 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: _q, unit_ref, city, postcode, unit_status, unit_vacant.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument unit_vacant is unclear.vague_boolean

arthur_list_tenants

54 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
15 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: email, mobile, full_address.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

arthur_list_tasks

56 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: _q, assigned_to, task_type.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

arthur_list_tenancies

56 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
17 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    Arguments without a description: _q, status, full_address.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

arthur_list_certificates

59 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Minor
    No `required` list, so every argument is optional.no_required

arthur_list_transactions

63 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
16 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: status, statement, transaction_type.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

arthur_list_invoices

64 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
17 / 25
Return value
7 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: status, submitted.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The meaning of the boolean argument submitted is unclear.vague_boolean

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers