Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · SONGMICS 6-Tier Large Jewelry Case with Drawers

tds_purchase_a12
Read-onlyIdempotent

Recorded model UJBC152. Use the seller’s model field or exact variant name. Use measurements for the exact variant, including required clearances.

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": {
      "offeredModel": "<offeredModel>",
      "itemWidthCm": "<itemWidthCm>",
      "itemDepthCm": "<itemDepthCm>",
      "itemHeightCm": "<itemHeightCm>",
      "innerWidthCm": "<innerWidthCm>",
      "innerDepthCm": "<innerDepthCm>",
      "innerHeightCm": "<innerHeightCm>",
      "paddingCm": "<paddingCm>"
    },
    "name": "tds_purchase_a12"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/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 covered. Beyond that, the description adds nothing about how a fit check computes clearance, what a negative or marginal result means, or how the interior measurements relate to the padding. For a calculation tool, that leaves important behavior unexplained.

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

Conciseness4/5

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

Three short sentences that are front-loaded with the concrete model number, and nothing is padded or repetitive. The opening 'Recorded model UJBC152' is a bare assertion with no verb, so it adds little beyond the title. Otherwise the size is proportionate to the content.

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 an 8-parameter, all-required fit calculator with no output schema, 0% schema coverage, and no explanation of the result. The description covers only model selection and one hint about clearances, then stops, so it is not sufficient for an agent to call the tool confidently or interpret what comes back.

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 8 required parameters, so the description has to compensate, and it only partly does. It clarifies offeredModel (seller's model field or exact variant name) and implies paddingCm is the clearance allowance, but itemWidthCm, itemDepthCm, itemHeightCm, innerWidthCm, innerDepthCm and innerHeightCm get no explanation. It doesn't say whether interior dimensions come from the container spec, whether measurements are exterior or interior, or how paddingCm is applied.

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 never states the operation — it opens with 'Recorded model UJBC152' and then only gives input-sourcing rules. The purpose ('check storage fit') comes from the title and from the phrases 'measurements for the exact variant' and 'required clearances', so it is implied rather than stated. An agent can guess this is a fit-check tool, but the description itself doesn't say so.

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

Usage Guidelines3/5

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

There is a real precondition: use the seller's model field or exact variant name, and use measurements for the exact variant including clearances, so no approximate or generic numbers. That implicitly tells the agent when the tool applies: only when exact-variant data is available. It never compares this to alternatives. The many sibling tds_purchase_* tools are not mentioned, and nothing says whether to run one fit check per variant.

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.