All scored servers

SCVD General Store: tool descriptions scored store.scvd/general-store

tools/list taken
(UTC)
Connected to
https://scvd.store/mcp
Homepage
scvd.store
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how SCVD General Store (store.scvd/general-store)'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/store.scvd/general-store
Average score
77.4 / 100Clear
Tools
21
Near-identical descriptions
1

Across the server

  • Minor
    The server's instructions are 3541 characters. Claude Code reads only the first 2,048 by default (Codex 0.154.0 reads them whole). Put what the server is for first.instructions_long

Tools whose descriptions are nearly the same

1 of 1 pairs shown, highest description similarity first.
ToolToolDescription similarityName similarity
buy_mandatebuy_memory_anchor0.600.25

Tools

ring_bell

66 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
22 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • Minor
    No `required` list, so every argument is optional.no_required
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

check_order

67 / 100Cloudy

Purpose
20 / 20
When to use
0 / 20
Arguments
25 / 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
    Required identifiers whose description does not say where the value comes from: order_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

look_in_window

69 / 100Cloudy

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10

No issues.

check_a2a_card

70 / 100Clear

Purpose
20 / 20
When to use
0 / 20
Arguments
25 / 25
Return value
15 / 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

check_purchase

70 / 100Clear

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

check_before_you_pay

72 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

find_in_catalog

72 / 100Clear

Purpose
20 / 20
When to use
5 / 20
Arguments
22 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Minor
    No `required` list, so every argument is optional.no_required

preflight_endpoint

72 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

look_at_door

74 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10

No issues.

read_store_guide

74 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10

No issues.

read_binder

75 / 100Clear

Purpose
20 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

sign_guestbook

77 / 100Clear

Purpose
20 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10
  • Minor
    The description mentions none of its 3 or more arguments.params_not_in_description

buy_observation

80 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    The description is long (936 words). It helps selection but costs steps and tokens.too_long

buy_human_task

82 / 100Clear

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

buy_small_pleasure

82 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    The description is long (417 words). It helps selection but costs steps and tokens.too_long
  • Minor
    Required identifiers whose description does not say where the value comes from: item_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

verify_artifact

82 / 100Clear

Purpose
20 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
0 / 10
  • 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

check_conformance

84 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
7 / 10
Examples
5 / 10

No issues.

buy_signed_record

87 / 100Clear

Purpose
17 / 20
When to use
10 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    The description is long (438 words). It helps selection but costs steps and tokens.too_long
  • Minor
    Required identifiers whose description does not say where the value comes from: item_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

buy_simple

87 / 100Clear

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

buy_mandate

91 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
24 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    Its description is nearly the same as buy_memory_anchor's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use buy_memory_anchor instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: item_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

buy_memory_anchor

92 / 100Clear

Purpose
17 / 20
When to use
15 / 20
Arguments
25 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Minor
    Its description is nearly the same as buy_mandate's (similarity 0.60); only the names and schemas tell them apart. Say in this description when to use buy_mandate instead.confusable_pair
  • Minor
    Required identifiers whose description does not say where the value comes from: item_id. Name the tool or the place that returns it, or models look it up first.id_source_missing

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