All scored servers

ATTRACTOR Verification, State & Evidence: tool descriptions scored io.github.NovanBaillif/attractor-machine-commons

tools/list taken
(UTC)
Connected to
https://attractor-observatory-demo.vercel.app/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how ATTRACTOR Verification, State & Evidence (io.github.NovanBaillif/attractor-machine-commons)'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.github.NovanBaillif/attractor-machine-commons
Average score
63.2 / 100Cloudy
Tools
20
Near-identical descriptions
1

Across the server

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
canonicalize_jsonfingerprint_json0.740.33

Tools

contribute_solution

49 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
9 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    Arguments without a description: problem, problem.title, problem.output_schema, solution, solution.slug, solution.recipe, solution.recipe.fields, solution.recipe.fields[].from, solution.recipe.fields[].to, solution.recipe.fields[].steps, solution.examples, solution.examples[].input, solution.examples[].expected, solution.parent_id, solution.exposure_id, solution.conventions.param_no_description
  • Minor
    String arguments with no constraint or example: problem.title, solution.slug, solution.recipe.fields[].from, solution.recipe.fields[].to.loose_string_param
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

find_evidence

52 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
12 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: id, capability, kind, limit.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

read_solution

52 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
8 / 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
    Arguments without a description: id.param_no_description
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description
  • 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

find_solutions

54 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
12 / 25
Return value
15 / 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
  • Major
    Arguments without a description: query, input, output_schema, limit.param_no_description
  • Minor
    No `required` list, so every argument is optional.no_required

check_observation

56 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
16 / 25
Return value
8 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: about, receipt, replay.param_no_description

verify_reuse

58 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
14 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: id, exposure_id, marker, input, output.param_no_description
  • Minor
    Required identifiers whose description does not say where the value comes from: id, exposure_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

verify_artifact

62 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
20 / 25
Return value
15 / 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
    Arguments without a description: artifact, state_id.param_no_description

coerce_to_schema

63 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
16 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: value, schema, decimal_comma.param_no_description
  • Minor
    The meaning of the boolean argument decimal_comma is unclear.vague_boolean

map_fields

63 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
16 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: value, mapping, omit_missing.param_no_description
  • Minor
    The meaning of the boolean argument omit_missing is unclear.vague_boolean

retrieve_state

63 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
16 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Major
    Arguments without a description: id, query, limit.param_no_description

validate_schema

65 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: value, schema.param_no_description

canonicalize_json

67 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as fingerprint_json's (similarity 0.74); only the names and schemas tell them apart. Say in this description when to use fingerprint_json instead.confusable_pair
  • Minor
    Arguments without a description: value.param_no_description

fingerprint_json

67 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Its description is nearly the same as canonicalize_json's (similarity 0.74); only the names and schemas tell them apart. Say in this description when to use canonicalize_json instead.confusable_pair
  • Minor
    Arguments without a description: value.param_no_description

flatten_json

67 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: value.param_no_description

share_state

67 / 100Cloudy

Purpose
20 / 20
When to use
5 / 20
Arguments
15 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Major
    Arguments without a description: artifact, visibility, title, kind, tags, parent_id.param_no_description

dedupe_records

70 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: records, keys.param_no_description

diff_json

70 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: before, after.param_no_description

find_capability

70 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
18 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: query, limit.param_no_description
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

extract_json

72 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    Arguments without a description: text.param_no_description

record_observation

77 / 100Clear

Purpose
20 / 20
When to use
10 / 20
Arguments
20 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    Arguments without a description: record.param_no_description

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