Skip to main content
Glama

Market snapshot

get_market_snapshot
Read-onlyIdempotent

A one-call brief on an airport's car hire market this morning. Per car type: the typical daily rate, the cheapest and dearest pick-up days in the next 14 and the gap between them, and weekend against weekday. Plus the number of brands, the best-rated and lowest-priced brands, and events and holidays in the window. Useful for a marketing brief, a morning operations check or a pricing meeting.

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": {
      "airport": "<airport>"
    },
    "name": "get_market_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportYesIATA airport code, e.g. AKL, SYD, LHR, MAD. See list_airports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds real behavioral scope beyond that: the data is a point-in-time ('this morning') read and the comparison window is bounded at 'the next 14', which materially shapes how results should be interpreted. No cost, rate-limit or response-shape notes, but none are needed for a read-only snapshot.

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?

Two sentences, front-loaded with the core promise and then a packed enumeration of the payload followed by use cases. The middle list is dense but every item is substantive output content rather than filler, so it stays close to optimally sized.

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?

With no output schema, the description carries the full burden of explaining return values and it does so thoroughly: per-car-type rates, min/max days and the gap, weekend/weekday split, brand count, best-rated and lowest-priced brands, plus events and holidays. An agent can predict the shape and content of the result before calling.

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?

There is a single parameter with 100% schema description coverage, including the IATA format example and a pointer to list_airports, so the schema does the work. The description only implies the airport scoping ('an airport's car hire market') and adds no format or validation detail beyond the schema, which is the baseline case for full coverage.

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 opens with a concrete verb+resource: 'a one-call brief on an airport's car hire market this morning', then enumerates exactly what that brief contains (per-car-type daily rate, cheapest/dearest pick-up days over the next 14 days, weekend vs weekday, brand counts, events). This clearly marks it as an aggregated snapshot rather than a single-metric tool, though it never names a sibling (e.g. get_market_rates, compare_airports) to draw the boundary explicitly.

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 closes with concrete usage contexts: 'a marketing brief, a morning operations check or a pricing meeting', which tells an agent the intended situations clearly. There are no exclusions or explicit 'use X instead when...' rules, so it stops short of the top score.

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