Skip to main content
Glama

Estimate used value

estimate_used_value
Read-onlyIdempotent

Calculate Valumech's illustrative used-value range for a delivered, publicly priced robot. This is a modeled placeholder, not an appraisal or resale comp.

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": {
      "robot": "<robot>",
      "ageYears": "<ageYears>",
      "condition": "<condition>"
    },
    "name": "estimate_used_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
robotYesCatalog ID or a sufficiently specific maker and model name.
ageYearsYesRobot age in years; decimals such as 0.5 are allowed.
conditionYesCurrent condition using Valumech's four condition bands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds valuable behavioral context beyond that: the result is a 'modeled placeholder, not an appraisal or resale comp,' which warns the agent not to treat the output as authoritative. It does not mention rate limits or precision caveats.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two tight sentences, no filler, with the core capability front-loaded and the critical disclaimer immediately following. Every clause earns its place.

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

Completeness4/5

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

All three required params are documented in the schema and no output schema exists, so the description partly compensates by telling the agent it returns a range. Combined with the placeholder disclaimer, the definition gives an agent enough to call and interpret the tool correctly.

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 100%, so robot, ageYears and condition are fully documented in the schema, including the enum bands and the 0-20 range. The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a specific verb ('Calculate') and resource ('illustrative used-value range') scoped to delivered, publicly priced robots. This is clearly distinct from siblings like get_robot_price and compare_robots, though no sibling is named explicitly.

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?

Use context is implied by the phrase 'used-value range for a delivered, publicly priced robot,' but there is no explicit when-to-use guidance or routing against get_robot_price / compare_robots. An agent must infer that this is for post-purchase valuation rather than pricing.

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.

Resources