Skip to main content
Glama

Find a robot to rent

find_rental
Read-onlyIdempotent

Robots to rent for events (with operator) in the user's country or city: from-prices (net), what they cover, the Antarum rental page and how fast Antarum answers. Rental firms stay unnamed until they make an offer.

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": "find_rental"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city, e.g. Berlin or Hamburg.
robotNoOptional id or name, e.g. "unitree-g1".
countryNoISO 3166-1 alpha-2 code, e.g. DE, AT, CH, GB, US, AE. Default: DE.
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a safe, read-only, idempotent lookup. The description adds two genuinely useful behavioral facts: rental firms remain unnamed until they make an offer, and results show response speed. It says nothing about pagination or result limits, so beyond the annotations the disclosure is modest.

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?

It is a single compact statement, front-loaded with the resource and the result shape. It is dense, but nearly every clause carries information (prices net, unnamed firms, answer speed), so there is little waste to cut.

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 properly explains what comes back: from-prices, what they cover, the rental page, and response latency. Combined with annotations covering safety and a mostly documented 4-param schema, it is close to complete, with only pagination/limits and sibling routing left as gaps.

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 75% and the schema already documents city, robot, country (with the DE default), and the language enum. The description adds scope meaning — that country or city localizes the market and that rentals are operator-included — but no format or precedence detail beyond the schema. The 3 baseline applies.

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?

The description states a specific resource and scope: robots available for rent for events, with an operator, in the user's country or city, and the kinds of results (from-prices, coverage, page, response speed). It does not name a sibling (get_robot, search_robots) to distinguish itself, so the differentiation is left to the reader.

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 implies when the tool applies — event rentals with an operator, localized to a country or city — but gives no explicit when-not conditions and no pointer to alternatives such as compare_robots or send_inquiry. An agent can infer the context, but nothing steers it away from misuse.

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