Skip to main content
Glama

The Doll Scout Home Tools

Check kitchen space · ThermoWorks ThermoPop 2 instant-read thermometer

tds_purchase_c02
Read-onlyIdempotent

Recorded model ThermoPop 2. 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_c02"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
shelfDepthCmYes
productDepthCmYes
useClearanceCmYes
frontClearanceCmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 structurally. Beyond that the description adds nothing behavioral: it does not say what the call returns, whether insufficient clearance yields an error or a verdict, or whether anything is persisted despite the "Recorded model" phrasing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, which is appropriate for a narrowly scoped helper. However, leading with a bare product-name fragment rather than the action weakens the front-loading.

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

Completeness3/5

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

For a 5-required-parameter, 0%-coverage tool with no output schema, this is thin: the agent knows roughly which values to supply but not their precise meaning or what result to expect. What is present (exact-variant sourcing, include required clearances) is correct and relevant, so it is not wholly inadequate.

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 5 required parameters, so the description must carry the meaning and largely does not. It hints that offeredModel should be the seller's model name and that the four *_Cm values are measurements "including required clearances," but never distinguishes shelfDepthCm from productDepthCm or useClearanceCm from frontClearanceCm, nor explains how they are compared.

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 body opens with the fragment "Recorded model ThermoPop 2," which names a product but not an action; the actual purpose (checking whether the thermometer fits a kitchen shelf/space) is only recoverable from the title. An agent can guess it is a fit/clearance check but the description itself never says so with a verb+resource.

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 description gives input-sourcing advice ("use the seller's model field or exact variant name") but never says when to call this tool versus a sibling, nor what happens when clearances fail. No exclusions or alternatives are named, so routing must be inferred from the product-specific name.

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.