Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Stasher Pocket Bag

tds_purchase_m_stasher_reusable_silicone_pocket_bag
Read-onlyIdempotent

Recorded model Pocket Bag. 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>",
      "shelfDepthCm": "<shelfDepthCm>",
      "productDepthCm": "<productDepthCm>",
      "useClearanceCm": "<useClearanceCm>",
      "frontClearanceCm": "<frontClearanceCm>"
    },
    "name": "tds_purchase_m_stasher_reusable_silicone_pocket_bag"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description's help. The description adds nothing about what the tool actually does with the measurements, whether it evaluates clearances or merely stores them, or what a caller gets back. "Recorded model" is ambiguous enough to be unhelpful, though not a direct contradiction of readOnlyHint.

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?

Two short sentences with no padding, but the front-loaded sentence is the least informative part of the definition. The useful constraints (exact variant name, variant-specific measurements) are buried after an opaque lead.

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?

Five required numeric/string parameters, no output schema, and no clarification of the tool's outcome. An agent knows what values to supply in the abstract but not what the tool computes or how to interpret a result, which is a significant gap for a measurement-driven fit check.

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 description coverage is 0% across five required parameters, so the description must carry the load. It does touch all five conceptually — the model field must be the seller's model or exact variant name, and the four numeric fields are "measurements for the exact variant, including required clearances" — but it never assigns meaning per field or clarifies how useClearanceCm differs from frontClearanceCm.

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

Purpose2/5

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

The description opens with "Recorded model Pocket Bag," which restates the product name rather than stating the operation. The title hints at "Check kitchen space," but the description never says whether this records a product, evaluates fit against a shelf, or returns a clearance verdict, so an agent cannot confidently distinguish it from the many sibling Stasher bag tools.

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 partial input guidance ("use the seller's model field or exact variant name," "use measurements for the exact variant"), but no statement of when this tool should be chosen over the sibling bag tools or over tds_quote_storage_space. No prerequisites, no exclusions, no context about the fit-checking workflow.

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.