Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Anker Nano Power Bank (30W, Built-In USB-C Cable)

tds_purchase_b18
Read-onlyIdempotent

Recorded model A1259. 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_b18"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior; the description adds that this is arithmetic only and warns that voltage, connectors, per-port limits and the setup guide must be checked separately. It still does not describe the result (pass/fail, margin, etc.) or model validation.

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?

The description is very short and largely free of filler, with each sentence carrying model, input, operation or caveat information. The purpose appears after model/input instructions rather than being front-loaded, and the fragment 'Recorded model A1259' is slightly awkward.

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 five required numeric parameters with no schema descriptions and no output schema, the definition is too thin: it omits units, reservedWatts semantics, and the return value. The caveat is useful, but it does not compensate for the missing schema detail.

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 description coverage, the description partly maps offeredModel and the budget/device-load parameters, but never mentions reservedWatts and gives no units or ranges. It leaves an agent guessing the semantics of at least one required numeric parameter.

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 description states the operation as an arithmetic comparison of a declared continuous allowance against provided device loads and anchors it to recorded model A1259. The product is identifiable via the model/title, though the description itself never says 'power bank' or 'Anker' and does not explicitly differentiate from sibling product tools.

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 provides an input-selection instruction (seller’s model field or exact variant) and a caveat to check voltage, connectors, per-port limits and the setup guide, which implies when the arithmetic is appropriate. It does not state when to choose this over sibling product tools or when not to use it.

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.