Skip to main content
Glama

The Doll Scout Home Tools

Measure photo support payload · Ulanzi VideoFast Heavy Duty Tripod Kit

tds_purchase_m_ulanzi_heavy_duty_tripod_videofast
Read-onlyIdempotent

Recorded model VideoFast Heavy Duty Tripod Kit. 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_m_ulanzi_heavy_duty_tripod_videofast"
  }
}

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, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is covered. The description does add genuine scope limits (dynamic loads, balance and mounting need a separate check), which is real value. It still does not state what the computation returns or how the reserve is applied.

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 no filler, but the opening sentence is a near-tautological restatement of the title and the payload purpose should have been front-loaded. The most informative content (the out-of-scope caveat) arrives last.

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?

For a tool with five required numeric inputs, no schema descriptions and no output schema, the definition is thin: it omits units, what value is returned, and how desiredReserveGrams alters the comparison. An agent could call it, but could not confidently predict the result semantics.

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% for all five required parameters, so the description carries the full burden. It clarifies offeredModel ('seller's model field or exact variant name') and loosely maps ratingGrams and the weight inputs, but cameraGrams, attachmentsGrams and especially desiredReserveGrams are never explained, leaving the agent to guess at units and role.

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 says 'Compare weights with a manufacturer rating for the exact configuration,' which conveys a payload-versus-rating comparison, but the opening 'Recorded model VideoFast Heavy Duty Tripod Kit' restates the title rather than stating a verb. The actual operation — computing whether camera plus attachments fit within the tripod's rating with a reserve — is only implied.

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' tells the agent how to populate the model identifier, and the closing sentence usefully exclaims that dynamic loads, balance and mounting are out of scope. However, it never names an alternative tool or a condition that would send the agent elsewhere, so the when-to-use guidance remains implicit.

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.