Skip to main content
Glama

The Doll Scout Home Tools

Check storage fit · Bankers Box Stor/File Basic-Duty Letter/Legal Storage Box

tds_purchase_a15
Read-onlyIdempotent

Recorded model 00703. 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_a15"
  }
}

Input Schema

NameRequiredDescriptionDefault
paddingCmYes
itemDepthCmYes
itemWidthCmYes
innerDepthCmYes
innerWidthCmYes
itemHeightCmYes
offeredModelYes
innerHeightCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds useful context that the model and measurements must correspond to the exact variant and include required clearances, but it does not explain how storage fit is determined or what the result will look like.

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?

The description is short and front-loaded with the recorded model identifier, then moves directly to variant and measurement instructions. There is little wasted wording, though the first sentence is an identifier rather than a purpose statement and the structure could connect the sentences more clearly.

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 fit-check tool with eight required numeric/string parameters and no output schema, the description is too thin. It does not explain the difference between item dimensions, inner dimensions, and padding, nor does it describe the fit logic or expected result, leaving an agent without enough information to invoke the tool confidently.

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

Parameters4/5

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

Schema description coverage is 0% for eight required parameters, so the description must carry parameter meaning. It explains offeredModel as the seller’s model field or exact variant name and says measurements should be for the exact variant including clearances, but it does not distinguish item dimensions from inner dimensions or explain paddingCm.

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 title supplies the action ("Check storage fit") and the specific product, but the description itself does not state the verb or explain what fit is being checked. It mostly gives input-selection instructions ("Recorded model 00703", "Use the seller’s model field or exact variant name"), leaving the purpose only implied.

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?

The description gives some invocation guidance by saying to use the seller’s model field or exact variant name and measurements for that variant, including clearances. However, it never states when this tool should be used instead of alternatives, nor does it name any sibling tool or exclusion condition.

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.