Skip to main content
Glama

Price index (not yet published)

get_price_index
Read-only

The MDJ price index is not yet published. For a price range use estimate_trip, and for a real price start_trip_request.

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

Input Schema

NameRequiredDescriptionDefault
partyNoOptional: solo, couple, family (with children) or group (3 or more adults).
tableNoOptional: return one whole table.
trip_daysNoOptional: length of the trip in days.
hotel_levelNoOptional. mix = a mix of 4-star and 5-star hotels.
start_monthNoOptional: month the trip starts, 1 to 12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds crucial behavioral context: the tool is unavailable because the index is unpublished. It does not specify what a call would return or whether it errors, but for an unavailable read-only tool the key status is disclosed.

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?

Two sentences, front-loaded with the tool's status and followed immediately by the alternatives. No filler or repetition.

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?

Given the tool is explicitly unavailable and has no output schema, the description does the essential job of preventing a wasted call and directing the agent to the right sibling. A minor gap remains around call behavior (error vs. empty response), but the core need is met.

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% and describes all five optional parameters with enums and constraints. The description adds no parameter-specific meaning beyond that, so the baseline of 3 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 identifies the resource as the MDJ price index and immediately states its status: not yet published. This distinguishes it from sibling tools like estimate_trip and start_trip_request, though it does not explain what the index would contain once published.

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?

It explicitly routes the agent away from this tool and names the correct alternatives: estimate_trip for a price range and start_trip_request for a real price. The implication that this tool should not be used is clear from 'not yet published.'

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