Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Klean Kanteen Tumbler Lid

tds_purchase_m_klean_kanteen_tumbler_lid
Read-onlyIdempotent

Recorded model Tumbler Lid. 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_klean_kanteen_tumbler_lid"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds only the hint that 'required clearances' are part of the check; it never says what the tool returns (fit/pass-fail), what happens when clearances are exceeded, or that all fields are mandatory.

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 with no bloat, but the opening 'Recorded model Tumbler Lid' is a wasted, tautological lead-in; the useful field-filling instructions should have been front-loaded.

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 five-required-parameter, zero-coverage tool with no output schema and no annotation help on inputs, the description is too thin. It should explain units, the geometry the check performs, and the meaning of each clearance figure; it does neither.

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?

With 0% schema description coverage across 5 required parameters, the description must carry the load. It meaningfully clarifies offeredModel (seller's model field or exact variant name) and that measurements should be for the exact variant, but leaves units, the distinction between shelfDepthCm/productDepthCm, and what useClearanceCm vs. frontClearanceCm represent undefined.

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 Tumbler Lid" mostly restates the name/title and never states a verb or the actual operation (verifying whether the tumbler lid fits on a shelf). The clearance-checking intent must be reverse-engineered from the parameter names, not the prose.

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 tell the agent how to fill two kinds of fields (seller model vs. exact variant name, and measurements for that variant), but give no guidance on when to invoke this tool, when not to, or how it relates to the numerous sibling product tools.

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.