Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Anker MagGo Wireless Charging Station (Foldable 3-in-1)

tds_purchase_b19
Read-onlyIdempotent

Recorded model A2557. 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_b19"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 real context by framing the call as pure arithmetic and warning that voltage, connectors, per-port limits and the setup guide are outside the computation — a meaningful scope boundary. It never says what the comparison returns or how a failure is signalled, which is a notable gap 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.

Conciseness4/5

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

Three short sentences, front-loaded with the identifying model number and then the purpose. Wording is efficient, though "Recorded model A2557" is fragmentary and the final sentence is a compressed list that could be clearer as a scope note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-required-parameter computation with no output schema, the definition explains the core operation and its boundaries but leaves reservedWatts undefined and the return format unspecified. An agent knows roughly what the tool does but not exactly what it will get back.

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%, so the description must carry all parameter meaning, and it only partly does: "declared continuous allowance" maps to continuousBudgetW and "provided device loads" maps to primaryDeviceW/otherDevicesW, and the model-name guidance covers offeredModel. reservedWatts is never explained, and no units or expected magnitudes are given beyond what the field names imply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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" states a specific operation (arithmetic comparison) on a specific resource (wattage budget vs. device loads), which an agent can act on despite the opaque tool name. It does not, however, distinguish this comparison tool from the surrounding catalog/purchase siblings.

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?

"Use the seller's model field or exact variant name" is guidance about a parameter value, not about when to call this tool versus another. There is no statement of prerequisites, exclusions, or an alternative tool for agents that lack a wattage budget.

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.