Skip to main content
Glama

Get a price quote

get_quote
Read-onlyIdempotent

Get the exact price for an activity, date, and party size, including tax, deposit due now, balance, and cancellation policy. Returns a quote_id that create_booking needs. Nothing is booked or charged.

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": {
      "activity_id": "<activity_id>",
      "date": "<date>",
      "participants": "<participants>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
activity_idYes
participantsYes
experience_levelNo
experience_durationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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. The description adds genuinely new behavioral context: the response fields returned and the quote_id handoff dependency to create_booking. It does not mention quote validity windows or any auth prerequisites, which keeps it from a 5.

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 tight sentences: purpose and returned fields first, then the downstream dependency, then the negative guarantee. No filler, and the most decision-relevant information is front-loaded.

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 usefully enumerates the return payload and the quote_id handoff, which is enough to call the tool correctly. The remaining gaps are quote expiration semantics and the two unexplained optional parameters, neither of which blocks invocation.

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 0%, so the description carries the burden, and it maps three of five parameters to concepts ('activity', 'date', 'party size' for participants). However experience_level and experience_duration appear nowhere in either the schema or the description, leaving 40% of the parameters without any meaning.

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 verb and resource ('Get the exact price for an activity, date, and party size') and enumerates what the response contains (tax, deposit due now, balance, cancellation policy). The closing 'Nothing is booked or charged' cleanly separates it from create_booking.

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?

Explicitly establishes the workflow context by saying the returned quote_id is what create_booking needs, which tells an agent to call this before booking. It lacks an explicit 'do not use this to actually book' exclusion or handling for expired quotes, but the read-only framing is clear.

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