Skip to main content
Glama

Compare robots

compare_robots
Read-onlyIdempotent

Compare two Valumech robots using sourced prices and specifications plus clearly labeled modeled depreciation. Returns a canonical or interactive comparison URL.

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": {
      "firstRobot": "<firstRobot>",
      "secondRobot": "<secondRobot>"
    },
    "name": "compare_robots"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstRobotYesFirst catalog ID or sufficiently specific robot name.
secondRobotYesSecond catalog ID or sufficiently specific robot name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds real value beyond them: it discloses data provenance (sourced prices/specs vs 'modeled' depreciation, clearly labeled) and the return shape (canonical or interactive URL).

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?

Two sentences, front-loaded with the compare action and ending with the deliverable. Slightly dense phrasing ('sourced prices and specifications plus clearly labeled modeled depreciation') but no 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?

For a two-parameter read-only tool, the description covers the action, the data sources, and the return (a URL), so no output schema is needed. It only lacks guidance on how this differs from the pricing siblings.

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 coverage is 100% and both parameters are documented as catalog ID or sufficiently specific robot name. The description only implies 'two robots' and adds no format, ordering, or resolution semantics 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?

Specific verb+resource: comparing exactly two Valumech robots, with a stated output (a comparison URL). It is distinguishable from siblings, but it does not explicitly contrast itself with get_robot_price or estimate_used_value even though it overlaps them on prices and depreciation.

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?

Usage is only implied by 'Compare two robots' – an agent can infer you call this when a head-to-head comparison is wanted. There is no explicit when-to-use/when-not guidance and no named alternative among the five siblings.

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