Skip to main content
Glama

The Doll Scout Home Tools

Measure photo support payload · Ulanzi GB5 Handheld Battery Grip P012

tds_purchase_m_ulanzi_p012_handheld_battery
Read-onlyIdempotent

Recorded model GB5 Handheld Battery Grip P012. 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_p012_handheld_battery"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraGramsYes
ratingGramsYes
offeredModelYes
attachmentsGramsYes
desiredReserveGramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/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. The description does add substance by disclosing the comparison basis (manufacturer rating for the exact configuration) and the scope limits around dynamic loads and mounting. It says nothing, however, about what the tool returns or how a marginal/reserve outcome is reported, which matters since no output schema exists.

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?

Four short sentences, front-loaded with the model identity, with no filler or repetition. Slight looseness in that the first sentence is a bare record statement rather than a purpose statement, but nothing is wasted.

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 five-parameter computation tool with no output schema, this description is thin: four of five inputs are undocumented and the result shape (margin, pass/fail, reserve surplus) is never described. The scope caveats help, but an agent could not confidently supply the weight and reserve inputs or interpret the response from this text alone.

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?

With 0% schema coverage and five required parameters, the description must carry the semantics. It only addresses offeredModel, leaving ratingGrams, cameraGrams, attachmentsGrams and desiredReserveGrams unexplained beyond the bare names; the phrase 'compare weights with a manufacturer rating' faintly implies which number is which, but the reserve parameter is never mentioned.

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 identifies the resource ('Recorded model GB5 Handheld Battery Grip P012') and gestures at an action ('Compare weights with a manufacturer rating for the exact configuration'), but never states plainly that this tool computes payload headroom or evaluates a support's suitability. An agent must lean on the title to know what the tool actually does, and no sibling tool is named for contrast.

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?

It says which identifier form to supply ('seller's model field or exact variant name') and gives one explicit exclusion — dynamic loads, balance and mounting are out of scope and need a separate check. That is a real boundary, but there is no positive 'use this when...' framing and no alternative tool named for the excluded cases.

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.