Skip to main content
Glama

ExducerAI GPU cloud

Quote a booking

quote_booking
Read-onlyIdempotent

What a booking would cost in CAD: GPU cost, tax and total for the whole duration, and the hourly rates. Books nothing and charges nothing. Always quote and show the user the total before create_booking.

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": {
      "server_id": "<server_id>",
      "gpus": "<gpus>",
      "hours": "<hours>"
    },
    "name": "quote_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
gpusYesNumber of GPUs: one of the server's allowed_gpu_counts.
hoursYesDuration in hours.
server_idYesServer id from list_servers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally; the description reinforces it with 'books nothing and charges nothing' and adds genuinely new context: currency (CAD), that the quote covers the whole duration, and which cost components are broken out. It stops short of noting quote expiry or whether prices can change between quote and booking, which would matter for a pricing tool.

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?

Three short sentences: what it returns, what it does not do, and the required workflow. The cost components are front-loaded and no sentence is redundant.

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 a simple three-parameter read-only tool with full annotation coverage and no output schema, the description supplies the returned fields and currency, which substitutes adequately for an output schema, plus the pre-booking workflow rule. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, with gpus tied to allowed_gpu_counts and server_id tied to list_servers, so the schema carries the semantics. The description only echoes duration via 'for the whole duration' and adds no unit or constraint detail beyond the structured fields.

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?

States a specific resource and the exact figures returned (GPU cost, tax, total, hourly rates) in CAD, and distinguishes itself from the mutating sibling by naming create_booking. An agent can tell instantly this is a pricing preview, not a reservation.

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?

Explicitly says 'Books nothing and charges nothing' and mandates quoting before create_booking, which is both a when-to-use rule and a named alternative. Nothing is left to inference about sequencing.

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