Skip to main content
Glama

The Doll Scout Home Tools

Measure photo support payload · Manfrotto PIXI EVO 2-Section Mini Tripod

tds_purchase_b25
Read-onlyIdempotent

Recorded model MTPIXIEVO-BK. 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_b25"
  }
}

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?

The annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds a useful behavioral caveat about what is not covered, but it does not explain how the comparison is performed, what constitutes a pass or fail, or what the agent should expect as a result.

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?

The description is short and includes useful caveats, but it is not front-loaded with a clear statement of purpose. The opening 'Recorded model MTPIXIEVO-BK' is cryptic without context, and the sentences read as scattered warnings rather than a structured explanation.

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 parameters, no output schema, and no parameter descriptions, the definition is incomplete. It omits the expected result of the comparison and leaves important inputs such as desiredReserveGrams unexplained, so an agent cannot confidently interpret or invoke the tool beyond the surface instruction.

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 zero schema description coverage across five required parameters, the description must carry the semantic burden. It partially clarifies the offeredModel field and the general role of weight/rating values, but it does not explain desiredReserveGrams, the source or meaning of ratingGrams, or how attachmentsGrams interacts with the calculation.

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 implies comparing supplied weights against a manufacturer rating for the recorded Manfrotto model, but it never plainly states the operation, such as checking whether camera plus attachments plus reserve fits within the rated payload. The model reference distinguishes it from other product-specific siblings, yet the purpose remains vague because the outcome is unstated.

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 gives a concrete usage instruction for the model field and warns that dynamic loads, balance, and mounting require a separate check, which helps limit misuse. However, it does not explicitly say when to use this tool versus any alternative or what to do if the model does not match.

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.