Skip to main content
Glama

GetBody

List robots for rent

list_bodies
Read-onlyIdempotent

List physical robot bodies available to rent from human body owners. No account needed: without credentials you get the public view (pricing, terms, access_options, coverage, rental_availability and approximate area; no exact location or owner identifiers). Signed in as an agent with a verified owner email you get the full view: exact location, body ids, command and feed schemas, live state per body and, with renter_lat/renter_lng, a delivery estimate. structuredContent.view says which view you got (view_reason when an agent is still pending). Use listing_id to inquire or request a rental. rental_availability is always, scheduled windows or on_request (inquire first).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bodies"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoKeywords; every word must appear in the robot type/model, notes, command names or descriptions.
limitNoPage size (default and max 200).
offsetNoSkip this many results (see total / truncated).
onlineNoOnly listings whose body is (true) or isn't (false) online now.
capabilityNoA declared capability (move, grip, see, hear_speak, other) or a command name the listing offers, e.g. 'grip' or 'mow'.
renter_latNoYour latitude, for the drop-off estimate (full view).
renter_lngNoYour longitude, for the drop-off estimate (full view).
robot_typeNoOnly bodies of this type (manifest.robot_type).
deliverableNoOnly real bodies that can (true) or can't (false) be delivered.
control_modeNo
interface_modeNoAvailable listings contain physical robots.

Output Schema

NameRequiredDescriptionDefault
codeNo
viewNo
errorNo
totalNo
bodiesNo
truncatedNo
retry_afterNo
view_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/non-destructive; the description adds substantial context they cannot convey: the listing is auth-dependent, the public view deliberately omits exact location and owner identifiers, structuredContent.view/view_reason reports which view you received, and pending agents get a specific reason code.

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?

Purpose and the no-account/full-view split are front-loaded, and every clause carries information (view fields, view_reason, rental_availability enumeration). It is dense with nested parentheses and runs long as a single block, which slightly hurts scannability.

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 an 11-parameter, output-schema-backed listing tool, the description covers what structured fields cannot: the anonymous/authenticated view duality, what is hidden in each view, how to detect a pending agent, the meaning of rental_availability, and the next step (listing_id to inquire or request). Return-value detail is correctly delegated to the output schema.

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 91%, so the baseline is 3. The description's only parameter-level addition is that renter_lat/renter_lng yield a delivery estimate in the full view, which the schema already states; filters like text, capability, online, robot_type and deliverable are left entirely to the schema. Adequate, but no meaning is added beyond structured fields.

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?

Opens with a specific verb and resource: 'List physical robot bodies available to rent'. The scope is concrete (rentable bodies, filtered listing) and the description signals the inquiry/rental handoff via listing_id, but it never names a sibling (e.g. find_robot_for_task) so the boundary with the task-matching tool is left implicit.

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?

Clearly explains the two usage contexts (anonymous public view vs. verified-owner agent full view) and when rental_availability means you must inquire first. It does not state explicit exclusions or name which alternative tool to use when you already know the task, so it stops short of full routing guidance.

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