Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · Klean Kanteen 12oz Camp Mug

tds_purchase_m_klean_kanteen_camp_mug
Read-onlyIdempotent

Recorded model 12oz Camp Mug. 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_camp_mug"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/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 nothing beyond that: it does not say what the tool computes, whether it returns a pass/fail fit verdict or a numeric comparison, or what the clearances are measured against.

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?

Two short sentences with no filler, so nothing is bloated. However, the first sentence spends its space on an item restatement rather than the operation, so the opening is not front-loaded with useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, no-output-schema, read-only tool with zero schema descriptions, this definition is under-built: an agent gets no explanation of what the clearance fields mean or of what a result looks like. Because the caller must supply every measurement blind, the description does not reach the minimum needed for confident invocation.

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 only hints that offeredModel accepts a seller model field or exact variant name and that measurements must match the exact variant; the four depth/clearance parameters (shelfDepthCm, productDepthCm, useClearanceCm, frontClearanceCm) are never distinguished or explained.

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 title says 'Check kitchen space', but the description never states a verb or an outcome; 'Recorded model 12oz Camp Mug' is a statement about the item, effectively restating the name. An agent can infer it compares product measurements against shelf space, but must infer it rather than read it.

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' is guidance about which value to pass, not about when to pick this tool over a sibling variant like tds_quote_storage_space or the 12oz_camp_mug_sale tool. No exclusions, prerequisites, or alternatives are named.

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.