Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Victorinox Swiss Classic Paring Knife

tds_purchase_c05
Read-onlyIdempotent

Recorded model 6.7603. 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_c05"
  }
}

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. Beyond that the description adds almost nothing: no indication of what the tool returns (a fit verdict?), what units measurements are in, or what happens when a variant is unknown or does not fit.

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?

Only three short sentences, so it is not bloated, but the lead sentence about the recorded model number is opaque and occupies the most prominent position. What little guidance exists is not front-loaded around the tool's actual action.

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 no output schema and zero schema documentation, an agent needs the description to explain the fit-check logic, units, and return shape; it explains none of these. For a five-required-parameter calculation tool, the definition is materially under-specified.

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% for five required parameters, so the description carries the full burden. It clarifies offeredModel (seller's model field or exact variant name) and gestures at the measurement parameters via "including required clearances", but never distinguishes shelfDepthCm, productDepthCm, useClearanceCm, and frontClearanceCm, nor states units or how clearances 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?

The description never states what the tool does. "Recorded model 6.7603" is product identity data, not a verb+resource, and the actual function (checking whether a knife/variant fits a kitchen space) is only recoverable from the title. An agent reading only the description cannot tell this apart from the many sibling tds_purchase_* 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?

The sentences "Use the seller's model field or exact variant name" and "Use measurements for the exact variant" are input-sourcing hints, not when-to-use guidance. There is no statement of when this tool applies versus siblings like tds_quote_storage_space, and no prerequisite or exclusion is 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.