Skip to main content
Glama

RoboSelect360 - Independent Humanoid Robot Intelligence

Robot profile (semiconductor coverage)

hardware_get_robot
Read-onlyIdempotent

Commercial profile of one robot (specs, pricing, viability score), plus whether a per-robot semiconductor bill of materials exists for it. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference. Also returns observed_capabilities: the evidence label per capability, as published on the robot's page; the observations behind the labels need get_robot_capabilities.

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_id": "<robot_id>"
    },
    "name": "hardware_get_robot"
  }
}

Input Schema

NameRequiredDescriptionDefault
robot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in return semantics: it explains that observed_capabilities are evidence labels as published on the page rather than raw observations. It does not cover behavior regarding missing data, error cases, or when a per-robot BOM does not exist, which matters for a tool whose title highlights 'semiconductor coverage.'

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?

Three sentences, front-loaded with the core resource and its returned fields, then disambiguation, then the cross-reference. The middle sentence about 'the layer flag' is the weakest link, since no such parameter exists, but overall there is no filler.

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

Completeness5/5

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

For a one-parameter read tool with no output schema, the description does the work the structured fields cannot: it enumerates the returned commercial fields, the BOM-existence flag, and the observed_capabilities structure with its evidence-label semantics. Combined with annotations that already establish the safety profile, an agent has enough to call this 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 coverage is 0% for the single required robot_id, so the description carries the burden. It implies the parameter selects exactly one robot ('profile of one robot'), which is a small clarification, but gives no format, no source for valid IDs (e.g., the list_robots sibling), and no behavior on an unknown ID.

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?

The description names a specific verb and resource (commercial profile of one robot) and enumerates the returned fields: specs, pricing, viability score, semiconductor BOM existence, plus observed_capabilities. It distinguishes itself from the other get_robot variants, but the differentiation rests on 'the layer flag,' which is not a parameter in the schema, so the mechanism of differentiation is fuzzier than it needs to be.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It routes the agent explicitly: use get_robot_capabilities for the observations behind the evidence labels. It also signals that the three get_robot variants differ only by layer, implying the prefix selects scope. What is missing is an explicit statement of when to choose this variant over mechanical_get_robot or software_get_robot, and any exclusion.

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.