Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Stasher Everyday Bag

tds_purchase_m_stasher_beauty_everyday_bag
Read-onlyIdempotent

Recorded model Everyday 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_beauty_everyday_bag"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/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 safety is covered. Beyond that the description adds essentially nothing: it does not say what is computed or returned (a pass/fail fit? a margin?), nor how the clearance values are combined, which is the core behavior of a space-checking tool.

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?

Three short sentences, so there is no bloat, and the model-identification advice comes first. However the fragments are choppy and the opening sentence ("Recorded model Everyday Bag") spends space on a label rather than on the operation, so the structure is efficient but not informative.

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?

With five mandatory parameters, no output schema, and no annotations describing the computation, the description would need to explain the fit logic and what the caller gets back. It instead leaves the central question — what the measurements are checked against and what result is produced — entirely unanswered.

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% with 5 required numeric/string parameters, so the description bears full responsibility. It gestures at offeredModel and at "measurements ... including required clearances" but never distinguishes shelfDepthCm, productDepthCm, useClearanceCm, or frontClearanceCm, nor explains units (cm) or how each should be measured.

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?

"Recorded model Everyday Bag" mostly restates the product name in the title rather than naming an operation; no verb (check, verify, record) tells the agent what the tool actually does. An agent cannot tell from the description whether this returns a fit verdict, stores measurements, or logs a purchase, and there is no differentiation from siblings such as tds_quote_storage_space.

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 only guidance is about inputs ("use the seller's model field or exact variant name"), which is parameter advice rather than when-to-use guidance. There is no statement of when this tool applies versus the many other Stasher model tools or the storage-space quote tool, and no prerequisites or exclusions are given.

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.