Skip to main content
Glama

The Doll Scout Home Tools

Project measured climate-device energy · GoveeLife Water Leak Detector 1s with Sensor Cable

tds_purchase_c25
Read-onlyIdempotent

Recorded model H5044 gateway + H5830 sensor. Use the seller’s model field or exact variant name. The estimate assumes the same use and conditions as your measured period.

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>",
      "measuredKwh": "<measuredKwh>",
      "measuredDays": "<measuredDays>",
      "projectedDays": "<projectedDays>",
      "tariffPerKwh": "<tariffPerKwh>"
    },
    "name": "tds_purchase_c25"
  }
}

Input Schema

NameRequiredDescriptionDefault
measuredKwhYes
measuredDaysYes
offeredModelYes
tariffPerKwhYes
projectedDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already state read-only, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds one estimate assumption but does not disclose the calculation basis, units, how tariff is applied, or what happens with unsupported or invalid model values.

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 each sentence is relevant, with no wasted prose. However, it is front-loaded with a model identifier rather than the action being performed, which weakens orientation.

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 a five-required-parameter calculation tool with no output schema and no parameter descriptions, the definition is incomplete. It omits units, calculation/projection method, and expected output, leaving an agent unable to invoke it confidently beyond repeating the model string.

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% for five required parameters. The description gives partial semantics for offeredModel (seller’s model field or exact variant name), but says nothing about measuredKwh, measuredDays, projectedDays, or tariffPerKwh units and relationships.

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 names the exact device and says 'The estimate assumes...', implying a projection, but never states the operative verb or the quantity being projected (energy use vs cost) in the description itself. The title supplies most of the purpose, so it is inferable, but not clearly differentiated from the many sibling purchase tools.

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?

Only input formatting guidance ('Use the seller’s model field or exact variant name') and a validity caveat ('same use and conditions as your measured period') are given. There is no statement of when to choose this projection tool over the many sibling purchase 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.