Skip to main content
Glama

The Doll Scout Home Tools

Measure photo support payload · Elgato Multi Mount Phone Grip

tds_purchase_b24
Read-onlyIdempotent

Recorded model Phone Grip. Use the seller’s model field or exact variant name. Compare weights with a manufacturer rating for the exact configuration. Dynamic loads, balance and mounting still need a separate check.

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>",
      "ratingGrams": "<ratingGrams>",
      "cameraGrams": "<cameraGrams>",
      "attachmentsGrams": "<attachmentsGrams>",
      "desiredReserveGrams": "<desiredReserveGrams>"
    },
    "name": "tds_purchase_b24"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraGramsYes
ratingGramsYes
offeredModelYes
attachmentsGramsYes
desiredReserveGramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile needs no restatement. The description adds that the comparison must be against a manufacturer rating for the exact configuration and that dynamic loads/balance are out of scope, but it never states the return shape for a read tool that clearly computes a comparison, and there is no output schema to compensate.

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?

Four short sentences with little waste, but the structure is weak: it opens with the contentless fragment 'Recorded model Phone Grip.' instead of a verb, and the remaining sentences read as scattered constraints rather than a front-loaded statement of what the tool returns.

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 five undocumented required numbers, no output schema and a computed result, the definition is under-specified for its complexity: it never explains how the grams are combined (camera + attachments + reserve versus rating), what units/verdict comes back, or what happens when the reserve is not met. The scope caveat is helpful but does not fill that gap.

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 must carry the meaning. It only glosses two of them: offeredModel ('seller's model field or exact variant name') and ratingGrams ('manufacturer rating for the exact configuration'). cameraGrams, attachmentsGrams and especially desiredReserveGrams — whose role in the total is the crux of the calculation — receive no explanation at all.

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 middle sentence ('Compare weights with a manufacturer rating for the exact configuration') implies the tool validates payload capacity for the Elgato Multi Mount Phone Grip, but the verb is buried and the opener 'Recorded model Phone Grip.' is a tautological fragment. An agent can guess the operation but is not told what it produces (a verdict, a margin figure, a pass/fail).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Dynamic loads, balance and mounting still need a separate check' is a genuine scope exclusion that tells the agent this tool does not answer those questions, which is useful routing signal. However, no alternative tool is named and no positive condition is given for when to reach for this instead of the many sibling purchase/measure 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.