Skip to main content
Glama

GetBody

Ask a body owner about rental details

create_inquiry

Ask a body owner about robot availability, pricing, delivery or rental requirements. Include a requested window and your message. Required first for listings whose rental_availability is on_request. Works for service rentals and offered remote arrangements before integration is ready. Reserves nothing. Read replies with get_inquiry or list_inquiries.

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": {
      "listing_id": "<listing_id>",
      "window_start": "<window_start>",
      "window_end": "<window_end>",
      "granted_permissions": "<granted_permissions>"
    },
    "name": "create_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional note to the host (max 500 chars).
body_kindNoWhich of the listing's bodies you are asking about; required when it offers both.
listing_idYes
window_endYesISO 8601 datetime, after window_start.
access_typeNo
control_modeNo
window_startYesISO 8601 datetime: the window you wanted.
granted_permissionsYesSubset of the listing's permissions_offered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / access_type
      Added value: +{
      +  "enum": [
      +    "onsite_operator",
      +    "remote_teleoperation",
      +    "equipment_only"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / body_kind / enum
      Previous value: -[
      -  "real",
      -  "simulated"
      -]New value: +[
      +  "real"
      +]
    • addedInput schema / properties / control_mode
      Added value: +{
      +  "enum": [
      +    "supervisory",
      +    "teleop",
      +    "onsite_operator",
      +    "equipment_only"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / control_mode
      Removed value: -{
      -  "default": "supervisory",
      -  "enum": [
      -    "supervisory",
      -    "teleop"
      -  ],
      -  "type": "string"
      -}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the safety profile is given. The description contributes beyond that with 'Reserves nothing' — a non-obvious side-effect disclosure — and the workflow prerequisite that this must precede other steps for on_request listings. It stops short of saying whether the inquiry expires, who can see it, or what an accepted reply implies.

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?

Five short sentences, each carrying a distinct fact: purpose, required inputs, the mandatory precondition, the supported scenarios, and the no-reservation guarantee. The prerequisite and the 'Reserves nothing' caveat are front-loaded where they matter.

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 an 8-parameter mutation with no output schema, the description covers purpose, precondition, side effects, and how to retrieve the reply, which is most of what an agent needs. The remaining gap is semantics for the enum-driven access and control parameters, which are left entirely to the 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 63%, and the description only restates that a requested window and a message should be included, which is already visible in the schema. It adds nothing on granted_permissions, body_kind, access_type or control_mode, so the undocumented third of parameters is not compensated for, though enum constraints do limit misuse.

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?

A specific verb (ask) plus the counterparty (body owner) and the exact subject matter: availability, pricing, delivery, rental requirements. It also names the read-side siblings get_inquiry and list_inquiries, so an agent can separate asking from reading without opening any schema.

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

Usage Guidelines5/5

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

Explicit about when this is mandatory ('Required first for listings whose rental_availability is on_request'), what contexts it covers (service rentals, offered remote arrangements before integration), and where to go for the answer (get_inquiry or list_inquiries). That is a clear when-to-use plus a named alternative.

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