Skip to main content
Glama

Get robot price

get_robot_price
Read-onlyIdempotent

Return Valumech's sourced new-price record, configurations, evidence date, availability, modeled used-value summary, and canonical page for one robot.

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>"
    },
    "name": "get_robot_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
robotYesCatalog ID or a sufficiently specific maker and model name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds data-provenance context ("Valumech's sourced", "evidence date", "modeled used-value") but says nothing about auth, rate limits, or error behavior for missing robots.

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?

A single sentence with the verb and primary payload front-loaded, and every clause names a distinct returned artifact. The return-field list is dense but not padded with filler.

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?

With no output schema available, the enumeration of returned fields (price record, configurations, evidence date, availability, used-value summary, canonical page) is genuinely load-bearing and tells the agent what a call yields. Missing only usage routing and failure semantics.

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% and the single parameter already documents accepted forms ("Catalog ID or a sufficiently specific maker and model name"). The description only reinforces the singular scope with "one robot," adding no syntax or matching-behavior detail beyond the schema.

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 ("Return") and an enumerated set of resources (sourced new-price record, configurations, evidence date, availability, modeled used-value summary, canonical page) scoped to "one robot." The scope makes it clearly a single-entity fetch rather than a search or comparison, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of the obvious alternatives in the sibling set (compare_robots, estimate_used_value, get_purchase_options, search_robot_catalog). The agent must infer that this is the lookup path once it already has a robot identifier.

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