Skip to main content
Glama

The Doll Scout Home Tools

Compare measured shelf load · Miniatures on a metal tray

tds_metal_tray_miniatures
Read-onlyIdempotent

Sum the item mass, supports and named extra load against a rating supplied by the user. Miniatures on a metal tray. Mass of the divider set (g).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "itemCount": "<itemCount>",
      "massPerItemG": "<massPerItemG>",
      "standMassG": "<standMassG>",
      "ratingG": "<ratingG>",
      "separatorMassG": "<separatorMassG>"
    },
    "name": "tds_metal_tray_miniatures"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingGYes
itemCountYes
standMassGYes
massPerItemGYes
separatorMassGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral content by disclosing the computation (item mass + supports + extra load compared against a rating), but it does not say what the comparison produces (pass/fail, margin, over-limit warning) and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler, but it is not front-loaded as a coherent statement: three sentence fragments follow the opening sentence, and the trailing "Mass of the divider set (g)." is an orphaned schema note rather than prose that earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter computational tool with no output schema and no annotation explaining results, the description should state the formula, units, and the shape of the result. It supplies a rough formula sketch but leaves the return value undefined and one parameter completely unaddressed, which is not enough for an agent to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for five required parameters. It gestures at item mass, supports, divider-set mass and rating, and the '(g)' hints at units, but itemCount is never mentioned, 'named extra load' maps to no existing parameter, and per-parameter units and value ranges are left unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a computable action (sum mass and compare against a user-supplied rating) which is more specific than the title alone, but the remaining fragments ("Miniatures on a metal tray", "Mass of the divider set (g)") read as scenario tags rather than purpose, and nothing distinguishes it from load-check siblings such as tds_spill_tray_display_load or tds_art_print_table_load.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g., that a rating must be known and supplied by the user), and no routing to any alternative sibling load tool. The only hint is the phrase 'rating supplied by the user', which implies preconditions but not alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.