Skip to main content
Glama

The Doll Scout Home Tools

Compare power allowance · Twelve South Curve Mini- Slate

tds_purchase_m_twelve_south_curve_mini
Read-onlyIdempotent

Recorded model Curve Mini- Slate. 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_m_twelve_south_curve_mini"
  }
}

Input Schema

NameRequiredDescriptionDefault
offeredModelYes
otherDevicesWYes
reservedWattsYes
primaryDeviceWYes
continuousBudgetWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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, non-open-world operation. The description adds useful context that it is an arithmetic comparison and that external hardware checks are expected, but it does not explain assumptions, result format, or error behavior. With annotations carrying the safety profile, this is adequate but limited.

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 short and front-loads the model variant, then gives input guidance, purpose, and a checklist. It is not bloated, though the first sentence is somewhat cryptic and the overall structure could be clearer.

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 arithmetic tool with no output schema, so the description should explain the calculation and what the agent gets back. It does neither in detail, and most parameters remain undocumented, making the definition incomplete 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 explain five required parameters. It gives meaning for offeredModel and loosely references continuous allowance and device loads, but it never defines reservedWatts, the relationship between primaryDeviceW and otherDevicesW, or units and calculation rules. Significant parameter ambiguity remains.

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 says the tool performs an arithmetic comparison between a declared continuous power allowance and provided device loads, which gives a concrete action and resource. However, the phrase “Recorded model” is vague, and it does not distinguish this tool from the many product-specific sibling variants or clarify what the comparison produces.

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 guidance is about using the seller’s model field or exact variant name, plus a checklist to verify voltage, connectors, per-port limits, and the setup guide. It does not say when to use this tool rather than another product tool, nor does it describe conditions under which the comparison should or should not be run.

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.