Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · OXO Good Grips 2-Cup Angled Measuring Cup

tds_purchase_c01
Read-onlyIdempotent

Recorded model 70981. 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_c01"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent, closed-world read with no side effects. The description adds one genuinely behavioral constraint, that the check is variant-specific and must include required clearances, but says nothing about what the result expresses (a pass/fail verdict, a shortfall amount?) despite there being no output schema.

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 low waste, but the opening "Recorded model 70981" is unexplained and takes the prime position without telling the agent what the tool does. The operational instructions are buried after it.

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 parameters with zero coverage and no output schema demand more than three sentences of instruction-level text. An agent cannot tell how a fit result is reported or what happens when a clearance is insufficient, which matters for a five-parameter all-required 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%, so the description must carry the load. It explains offeredModel well (seller's model field or exact variant name) and states the measurements must be for the exact variant, but it never disambiguates shelfDepthCm, productDepthCm, useClearanceCm, and frontClearanceCm, nor how the two different clearance values are used.

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

Purpose3/5

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

The description itself never states the action; it only says "Recorded model 70981" and gives input instructions. The purpose (checking whether this OXO measuring cup fits a kitchen shelf) has to be inferred from the title and the required clearance parameters, which is enough to guess but not to be told.

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?

"Use the seller's model field or exact variant name" and "use measurements for the exact variant" are data-entry rules, not usage guidance. Nothing says when to call this instead of a sibling such as tds_quote_storage_space, or what to do if measurements are unknown.

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.