Skip to main content
Glama

Pick-up days to promote or protect

get_promotion_days
Read-onlyIdempotent

For campaign planning: each of the next 14 pick-up days at an airport ranked against the window for a car type. Shows the typical market rate that day, how far it sits above or below the 14-day typical rate, how many offers are on sale, and any event or holiday on the day. Soft days are where a price-led offer has to work hardest; dear days are where demand is already paying.

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_promotion_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportYesIATA airport code, e.g. AKL, SYD, LHR, MAD. See list_airports.
categoryNoCar type key, e.g. compact, economy, suvs, intermediate, estate, fullsize, carriers_8. Car types: mini, economy, compact, intermediate, standard, fullsize, premium, luxury, suvs, estate, carriers_7, carriers_8, carriers_9, vans, pickups, convertibles (not every airport has every type).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description goes further by disclosing the exact output content and the fixed 14-day horizon plus the baseline it measures against, which is genuinely useful behavior context. It omits ranking direction details and pagination, keeping it below top marks.

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?

The purpose and audience are front-loaded in the opening clause, followed by a compact enumeration of returned fields. The final sentence earns its place by defining soft and dear days, though the piece runs slightly long for a two-parameter read tool.

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 must convey return values, and it does so precisely: rate, deviation from the 14-day typical, offer count, and any event or holiday. Combined with 100% schema coverage and clear read-only annotations, the agent has enough to select and call it correctly; only the ranking order and response size remain unstated.

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%, so both parameters are already documented with examples and a full car-type list, establishing the baseline of 3. The description only echoes the airport and car-type inputs conceptually and adds no format or edge-case guidance beyond the schema, which is acceptable but not additive.

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 states a specific resource and scope: the next 14 pick-up days at a named airport for a car type, ranked against the window, with the exact fields shown (typical market rate, delta vs 14-day rate, offer count, events/holidays). It is clearly distinguishable from nearby tools by framing the output as a day-by-day promote/protect ranking, though it never names a sibling outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"For campaign planning" establishes the intended context and the closing sentence explains what soft vs dear days mean for price-led offers, which implies when to reach for it. It stops short of stating when-not to use it or which sibling to prefer for raw rates, snapshots, or events, so the agent must infer the boundary.

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