Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Anker 735 Charger (Nano II 65W)

tds_purchase_b17
Read-onlyIdempotent

Recorded model A2667. 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_b17"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine boundary context by naming the factors it does not model (voltage, connectors, per-port limits, setup guide), which tells the agent this is a watts-only check. It still omits the return value, which matters given there is no output schema.

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, and the model-identification instruction is front-loaded. However, the sentences are telegraphic and disjointed — the jump from model naming to arithmetic to a checklist of cautions reads as 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?

With no output schema and no documented return behavior, the description leaves the agent unable to predict what the arithmetic produces. Combined with four of five parameters left undefined, the definition is not sufficient to invoke the tool confidently on first attempt.

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 coverage is 0% across five required numeric parameters, so the description carries the full burden. It clarifies only offeredModel (use the seller's model field or exact variant name); continuousBudgetW, primaryDeviceW, otherDevicesW, and reservedWatts are never explained, and it is unclear whether reservedWatts is subtracted or added.

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?

"This arithmetic compares a declared continuous allowance with provided device loads" does convey a specific operation, but the verb is abstract and the title's product framing ("Compare power allowance") is not reinforced. It never states whether the result is a boolean, a margin, or a pass/fail verdict, so the agent knows the shape of the computation but not its output.

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 directive — "Use the seller's model field or exact variant name" — is a parameter hint, not a when-to-use rule. "Check voltage, connectors, per-port limits and the setup guide" hints at things this tool does not cover, but no alternative or precondition is named, and nothing distinguishes this from the many sibling purchase tools.

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.