Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Stasher Gallon Bag

tds_purchase_m_stasher_gallon_bag
Read-onlyIdempotent

Recorded model Gallon 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_gallon_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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the call returns a fit/no-fit verdict, what happens when clearances fail, what units are assumed, or that the model string must match an exact SKU.

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?

At three short sentences there is no padding, but the opening sentence is wasted space restating the name, and the functional instruction is buried in the last clause rather than front-loaded. The structure is terse to the point of being cryptic rather than efficient.

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?

A five-required-parameter tool with no output schema and no annotation coverage of behavior needs the description to explain the units, the fit logic, and the expected result. Instead it leaves the agent guessing whether this records a purchase, validates a fit, or quotes space, which is insufficient for the tool's complexity.

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 carries the full burden. It gestures at the model field, variant measurements and 'required clearances,' which maps loosely to offeredModel and the clearance params, but it never distinguishes shelfDepthCm from productDepthCm or explains how useClearanceCm and frontClearanceCm are combined.

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 Gallon Bag,' which restates the tool name rather than naming an action. Only the phrase about 'required clearances' hints that this evaluates whether a product fits on a shelf, and the agent must borrow that verb from the title 'Check kitchen space' rather than the description itself.

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 call this tool versus the many sibling Stasher bag tools or the adjacent tds_quote_storage_space. The only guidance is parameter-level ('use the seller's model field or exact variant name'), which tells the agent nothing about tool selection or exclusions.

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.