Skip to main content
Glama

The Doll Scout Home Tools

Compare measured shelf load · Figures on a glass shelf

tds_glass_shelf_figures
Read-onlyIdempotent

Sum the item mass, supports and named extra load against a rating supplied by the user. Figures on a glass shelf. Protective mat mass (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>",
      "matMassG": "<matMassG>"
    },
    "name": "tds_glass_shelf_figures"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingGYes
matMassGYes
itemCountYes
standMassGYes
massPerItemGYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds that the rating is user-supplied (not looked up) and that protective mat mass is one of the summed terms, which is genuine behavioral context. It does not disclose the decision result or margin, leaving the agent unsure what the sum is reported against.

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

Conciseness2/5

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

It is short, but shortness here comes from omission rather than editing: three sentence fragments with no logical ordering, and the most important constraint (how itemCount interacts with massPerItemG) is absent. The '(g)' unit note dangles at the end instead of being attached to the relevant inputs.

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?

This is a computational tool with five required, fully undocumented parameters and no output schema, so the description carries the entire burden of explaining inputs and the computation. It fails to explain the multiplication by itemCount, the units of the rating, or what the result represents (total mass, margin, pass/fail). An agent could pass plausible numbers but cannot verify its interpretation is correct.

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% across five required numeric parameters, so the description must carry all semantics. It gestures at four of them (item mass, supports, extra/mat load, rating) but leaves itemCount completely unexplained and, critically, is ambiguous about whether massPerItemG is multiplied by itemCount or summed once. Units are only hinted at via '(g)' in a fragment, and no parameter is tied to its schema name.

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 states a specific operation (summing item mass, supports and extra load against a user-supplied rating), which is more than a restatement of the name. However, the trailing fragments 'Figures on a glass shelf.' and 'Protective mat mass (g).' are noun-phrase labels with no verb, so the overall purpose reads as partly assembled from keywords. It is distinguishable from sibling load tools in intent, but the phrasing is vague about what is actually produced.

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 statement of when to use this versus the many sibling load tools (tds_art_print_table_load, tds_display_riser_load, tds_spill_tray_display_load). The phrase 'against a rating supplied by the user' implies the caller must already have a manufacturer rating, but this is not framed as a prerequisite or an exclusion condition. The agent must infer usage entirely.

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.