Skip to main content
Glama

The Doll Scout Home Tools

Measure photo support payload · Ulanzi MT-44 Extendable Vlog Tripod (Upgrade)

tds_purchase_b23
Read-onlyIdempotent

Recorded model MT-44 2502B. 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_b23"
  }
}

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 a safe, read-only, idempotent, closed-world operation, so the description doesn't need to re-establish that. It does add useful scope context: the comparison is a static weight check against a manufacturer rating for one exact configuration, and dynamic loads, balance and mounting are explicitly out of scope. It stops short of saying what the call returns (margin, pass/fail) or how ties/near-limit cases behave.

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 padding, but the opening 'Recorded model MT-44 2502B' is data noise rather than guidance, and there is no front-loaded statement of what the tool actually computes. The telegraphic style reads like notes rather than a structured definition.

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?

This is a multi-input computation with five required, entirely undescribed parameters and no output schema. The description supplies the model-matching rule and an out-of-scope caveat but never explains the reserve parameter or the shape of the result, which leaves an agent unable to call it confidently or interpret the answer.

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% with five required numeric/string parameters, so the description must carry the semantics. It partially does: offeredModel is tied to the seller's model field or exact variant name, and ratingGrams is tied to the manufacturer rating for the exact configuration. cameraGrams, attachmentsGrams and especially desiredReserveGrams (the reserve concept is never explained) remain undocumented anywhere.

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 title carries most of the meaning ('Measure photo support payload'); the description only says 'Compare weights with a manufacturer rating for the exact configuration.' That implies a payload/headroom comparison but never states the verb-plus-outcome (e.g. 'computes whether camera + attachments fit within the tripod's rating with reserve'). The opaque name tds_purchase_b23 gives no help, and nothing distinguishes it from the many tds_purchase_m_* product siblings.

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?

'Use the seller's model field or exact variant name' gives a concrete input-selection rule for offeredModel, and 'Dynamic loads, balance and mounting still need a separate check' is a real scope exclusion. What is missing is when to reach for this tool at all versus the sibling tripod/purchase tools, and any prerequisite about where ratingGrams comes from.

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.