Skip to main content
Glama

list_rental_engines

List HOBO per-run services, including OpenAI text summaries, JSON extraction, translation, code review and rewriting. No buyer OpenAI key required. Provider consumption plus 100%; owner-authorized Stripe or verified crypto payment required.

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_rental_engines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does add real context: no buyer-side OpenAI key needed, provider consumption billed at +100%, and owner-authorized Stripe or verified crypto payment. However, it is ambiguous whether those payment requirements apply to this listing call itself or only to subsequent rental calls, which is exactly the kind of behavioral detail an agent needs before calling.

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 short sentences with the core purpose front-loaded, which is good. But the trailing payment sentence is dense and ambiguous about what it applies to, and jargon like 'HOBO' and 'provider consumption plus 100%' is not unpacked, so words are spent without fully earning clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool with no annotations and no output schema, the description must explain what the returned catalog looks like, and it only gestures at service names without indicating identifiers, pricing fields, or endpoint callability. The payment/pricing note is relevant but insufficiently tied to the tool's own behavior.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description also correctly implies no filtering inputs are needed.

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 concrete verb+resource ("List HOBO per-run services") and enumerates the service categories (summaries, JSON extraction, translation, code review, rewriting), so an agent knows what catalog is returned. It stops short of differentiating this listing from sibling catalog tools like list_products or quote_rental, and the name/description mismatch (rental_engines vs 'HOBO per-run services') adds friction.

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?

Usage is only implied: the mention of payment and pricing suggests this is the discovery step before quote_rental or create_rental_checkout, but the description never says when to call it versus those siblings or what prerequisites exist. No exclusions or ordering guidance are given.

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