Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Anker Nano Power Strip (10-in-1, 70W, Clamp)

tds_purchase_b21
Read-onlyIdempotent

Recorded model A9196. Use the seller’s model field or exact variant name. This arithmetic compares a declared continuous allowance with provided device loads. Check voltage, connectors, per-port limits and the setup guide.

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>",
      "continuousBudgetW": "<continuousBudgetW>",
      "primaryDeviceW": "<primaryDeviceW>",
      "otherDevicesW": "<otherDevicesW>",
      "reservedWatts": "<reservedWatts>"
    },
    "name": "tds_purchase_b21"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so safety needs no restating. What the description does add is a useful caveat that the arithmetic is not a full validation (check voltage, connectors, per-port limits, setup guide), but it never describes the return value or how results should be interpreted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, but the ordering is poor: the model-name detail is front-loaded while the actual function appears second. Fragmentary phrasing ('This arithmetic compares...', 'Check voltage, connectors...') leaves the agent to assemble the meaning, and the closing checklist is ambiguous about whether those steps are part of the call or follow-up work.

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 five-required-parameter computation with no output schema and no annotation detail about results, yet the description says nothing about what is computed or returned. For a tool whose whole value is a numeric verdict, the omission of output shape and interpretation guidance is a significant gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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/string parameters, so the description must compensate. It partially does: 'declared continuous allowance' maps to continuousBudgetW, 'provided device loads' hints at primaryDeviceW/otherDevicesW, and the model-name sentence clarifies offeredModel. reservedWatts is never explained, and no units or interaction between the watt fields are given.

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 sentence 'This arithmetic compares a declared continuous allowance with provided device loads' does describe the operation, but it is abstract and never states what the tool actually produces (headroom figure, pass/fail, list of violations). The opening 'Recorded model A9196' is a product identifier rather than a statement of function, so an agent has to infer the purpose from the title.

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

Usage Guidelines2/5

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

The only conditional guidance is parameter-level ('Use the seller’s model field or exact variant name'). There is no statement of when this tool should be chosen over the sibling product tools, no prerequisites, and no exclusion cases. 'Check voltage, connectors, per-port limits and the setup guide' reads as user advice rather than routing guidance for an agent.

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.