Skip to main content
Glama

quote_rental

Quote one immutable run. For agent text tasks use engine=openai and service_id=summarize_text, extract_json, translate_text, review_code or transform_text; put source text and instructions in brief. Small tasks can use api_budget_usd=0.10. Consumption plus 100%; verified prepayment required.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quote_rental"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefNo
filesNo
engineNo
componentsNo
model_tierNo
service_idNo
api_budget_usdNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.1/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 burden; it does disclose two real behavioral facts: pricing is "Consumption plus 100%" and "verified prepayment required." However, it never explains what "immutable" means in practice, whether quoting itself charges anything, how long a quote is valid, or how the required prepayment is verified — gaps 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.

Conciseness4/5

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

Three compact sentences with the routing hint front-loaded and no filler; the parameter clusters are grouped sensibly (engine/service_id, then brief, then budget). The telegraphic phrasing ("Consumption plus 100%") is dense but not padded.

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

Completeness2/5

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

For an 8-parameter tool with no annotations and no output schema, the definition leaves too much unresolved: what a quote returns (price, currency, expiry), what idempotency semantics apply to the required key, what files/components accept, and how the prepayment prerequisite connects to the verification siblings. The agent has enough to guess a happy-path text-task call but not enough to invoke it safely in general.

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

Parameters2/5

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

Schema description coverage is 0% across 8 parameters, so the description must compensate, and it only covers four: engine, service_id (with the enumerated text-task values), brief (source text and instructions), and api_budget_usd (a $0.10 small-task hint). The required idempotency_key is never mentioned, and files, components, and the model_tier enum are completely unexplained.

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

Purpose3/5

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

"Quote one immutable run" names a verb and an object, but "run" and "immutable" are undefined jargon that an agent cannot map onto the rental/checkout family of siblings. The concrete engine/service_id/brief guidance later in the description does more to reveal the actual purpose than the opening sentence does.

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 an explicit when-to-use rule ("For agent text tasks use engine=openai and service_id=summarize_text, extract_json, ...") plus a budget hint for small tasks. It stops short of stating when NOT to use this tool or naming an alternative sibling such as create_rental_checkout, so it is clear context without exclusions.

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