Skip to main content
Glama

The Doll Scout Home Tools

Compare measured shelf load · Books on a wooden shelf

tds_wood_shelf_books
Read-onlyIdempotent

Sum the item mass, supports and named extra load against a rating supplied by the user. Books on a wooden shelf. Mass of the bookends (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>",
      "bookendsMassG": "<bookendsMassG>"
    },
    "name": "tds_wood_shelf_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingGYes
itemCountYes
standMassGYes
massPerItemGYes
bookendsMassGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description need not restate it. It does add one useful behavioral fact — the rating is supplied by the user rather than looked up — which tells the agent this is a pure local computation. It says nothing about the comparison outcome or units of the result, so the added value is modest.

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, so there is no padding to trim, but the structure is poor: three disconnected fragments with no front-loaded statement of the computation or its result. The final fragment "Mass of the bookends (g)." reads like a leftover schema note rather than an organized description.

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-required-parameter calculator with no output schema and no parameter descriptions, the description leaves material gaps: it never states the sum formula, units for four of five inputs, or what the tool returns (boolean pass/fail, margin, or total mass). An agent could invoke it but could not predict its result.

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

Parameters3/5

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

Schema coverage is 0%, so the description carries the burden, and it does loosely map all five parameters: item mass (itemCount × massPerItemG), supports (standMassG), extra load (bookendsMassG), and the user-supplied rating (ratingG). However, "supports" vs. the schema's "standMassG" is an inexact match, and the only unit explicitly given is grams for bookends. The compensation is partial rather than reliable.

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 description names a real operation — summing item mass, supports and extra load, then comparing against a user-supplied rating — which is more than a restatement of the name. But key terms are undefined ("supports", "named extra load") and the trailing fragment "Books on a wooden shelf" adds domain flavor rather than purpose. An agent gets the gist but not a precise statement of what is being computed or returned.

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 guidance, no mention of when this calculator applies versus other load tools in the family, and no prerequisites or exclusions. The only implicit context is the shelf-and-books framing, which an agent must infer rather than read.

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.