Skip to main content
Glama

GetBody

Send a robot command

send_robot_command

Runs one command on the leased robot and returns the robot's result. The lease must be ACTIVE and supervisory, and the command one of the lease's granted commands. The robot acts in the physical world. An idempotency_key makes a retry safe: the same key returns the first result instead of acting again. If the robot reports a fault or doesn't answer, the lease is stopped.

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": {
      "lease_id": "<lease_id>",
      "command": "<command>"
    },
    "name": "send_robot_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoThe command's parameters, as its schema describes.
commandYesOne of the lease's granted commands, e.g. 'move'.
lease_idYesLease id.
idempotency_keyNoOptional: any string unique to this command; reuse it to retry safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the robot acts in the physical world, that an idempotency_key makes retries safe by returning the first result instead of re-acting, and that a fault or timeout stops the lease. Those are exactly the consequences an agent needs before invoking a non-read-only, open-world tool.

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

Conciseness5/5

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

Four tight sentences, front-loaded with what the tool does, then preconditions, then safety semantics, then failure behavior. No sentence is redundant.

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 mutating, open-world tool with a nested params object and no output schema, the description covers preconditions, retry safety, and failure handling well. It could say a bit more about what the returned 'result' looks like, but the essentials are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: idempotency_key is explained as a retry-safety mechanism, and command is constrained to the lease's granted commands. It does not explain the nested params object beyond deferring to the command's own schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Runs one command on the leased robot') and states that it returns the robot's result. That scope cleanly separates it from siblings like list_robot_commands (enumeration) and activate_lease (lease lifecycle), so an agent can pick it without opening the schema.

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 gives concrete preconditions for use: the lease must be ACTIVE and supervisory, and the command must be one of the lease's granted commands. It does not name an alternative tool or state when not to use it, which keeps it short of a 5.

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