Skip to main content
Glama

RoboSelect360 - Independent Humanoid Robot Intelligence

Robot profile (mechanical coverage)

mechanical_get_robot
Read-onlyIdempotent

Commercial profile of one robot (specs, pricing, viability score), plus its mechanical-profile status. 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": "mechanical_get_robot"
  }
}

Input Schema

NameRequiredDescriptionDefault
robot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is done; the description adds real value by enumerating what the payload contains (commercial fields, mechanical-profile status, observed_capabilities labels). It stops short of explaining what 'mechanical-profile status' values look like or the size/shape of the response.

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

Conciseness3/5

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

Front-loaded and reasonably tight, but the middle sentence about three get_robot variants and a 'layer flag' consumes space while referring to something absent from the schema, creating more confusion than clarity.

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, the description does the necessary work of listing the returned sections, and it correctly points at the companion tool for the deeper evidence. Only gaps are the meaning of the mechanical-profile status field and the robot_id format.

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?

There is a single required robot_id at 0% schema description coverage, and the description says nothing about its expected form (ID vs slug vs name) or where to obtain it. The concept of a per-robot lookup makes the parameter fairly self-evident, so this is adequate but not compensating for the coverage gap.

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 and resource ('Commercial profile of one robot (specs, pricing, viability score), plus its mechanical-profile status') and explicitly distinguishes itself from get_robot_capabilities for the underlying observations. It is slightly muddied by the claim that 'the commercial fields are identical in all three get_robot variants', which references variants and a 'layer flag' that the schema does not expose.

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?

Gives one useful routing rule – use get_robot_capabilities for the observations behind the labels – but never states when to choose this variant over the hardware/software get_robot siblings beyond the vague 'the layer flag is the only difference'. Usage is implied rather than stated.

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.