Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · TP-Link RE315 AC1200 Wi-Fi Range Extender

tds_purchase_b22
Read-onlyIdempotent

Recorded model RE315. 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_b22"
  }
}

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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds that the tool performs an arithmetic comparison and advises checking voltage, connectors, per-port limits, and the setup guide, but it does not explain the calculation result, units, edge-case behavior, or what the response contains.

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, but it is not front-loaded with the tool's purpose. It starts with an incidental model note and then mixes an arithmetic summary with a validation checklist, making the structure feel like a data annotation rather than a focused tool description.

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-parameter calculation tool with no output schema and no parameter descriptions, so the description should explain the calculation and return semantics. It does not explain how the allowance, loads, and reserved watts interact, nor what the agent should expect as output, leaving important gaps for correct invocation.

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 description coverage is 0%, so the description must carry the full burden for five required parameters. It only loosely maps the seller's model field to offeredModel, the declared continuous allowance to continuousBudgetW, and device loads to primaryDeviceW/otherDevicesW; it does not explain reservedWatts, the distinction between primary and other device loads, or how the values are combined.

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 eventually states that the tool performs an arithmetic comparison between a declared continuous allowance and provided device loads, which gives a vague sense of purpose. However, it opens with model-recording guidance and never uses a clear action verb or names the operation crisply, so it is not easy to distinguish from the many purchase-oriented 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?

The description gives input guidance such as using the seller's model field or exact variant name, plus a checklist about voltage, connectors, per-port limits, and the setup guide. It does not say when this tool should be used instead of alternatives, nor does it name any sibling tool or selection condition.

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.