Skip to main content
Glama

RoboSelect360 - Independent Humanoid Robot Intelligence

Robot profile (software coverage)

software_get_robot
Read-onlyIdempotent

Commercial profile of one robot (specs, pricing, viability score), plus its software tier and 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": "software_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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: which fields are guaranteed identical across the three layer variants, that the layer flag is the sole differentiator, and that observed_capabilities carries evidence labels without the underlying observations. It stops short of describing failure modes for an unknown robot_id.

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?

Three sentences, front-loaded with the payload contents, which is good. The middle sentence about a 'layer flag' is slightly confusing because the only parameter on this tool is robot_id — no layer flag is exposed — so that clause costs tokens without fully landing.

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?

No output schema exists, and the description compensates by enumerating the returned field groups (specs, pricing, viability score, software tier, profile status, observed_capabilities). Combined with the pointer to get_robot_capabilities for underlying observations, an agent has what it needs to call and interpret this reliably; only robot_id format is unaddressed.

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 parameter, robot_id, at 0% schema description coverage, and the description never discusses it — no format, prefix, or source guidance. The parameter is largely self-explanatory by name, so the gap is mild, but the description adds nothing beyond the schema here.

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 plus the exact contents of the payload: 'Commercial profile of one robot (specs, pricing, viability score), plus its software tier and profile status.' This lets an agent distinguish it from hardware_get_robot and mechanical_get_robot only indirectly, via the note that the commercial fields are shared across the three variants, rather than by an explicit statement of what the software layer uniquely adds.

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?

It gives one useful routing rule: the observations behind capability labels require get_robot_capabilities. However, it never says when to pick this software variant over hardware_get_robot or mechanical_get_robot, or when it should be skipped in favor of software_get_robot_software or software_list_robots, so selection between the layer variants is left to inference.

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.