Skip to main content
Glama

Trip Weather

get_trip_weather
Read-onlyIdempotent

Get trip weather. Daily detail returns a city-grouped forecast bounded to trip dates with confidence tiers; current or hourly detail returns observed or near-term conditions for one trip city. Provide trip_id from trips_list. The Tineo itinerary already shows each day's weather and refreshes it automatically as the trip gets closer.

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": {
      "trip_id": "<trip_id>"
    },
    "name": "get_trip_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHourly forecast horizon, default 12 hours. Used only when detail is hourly.
detailNoWeather detail. Default daily.
city_idNoTrip city ID, used for current or hourly weather. If omitted on a multi-city trip, the result lists available city IDs.
trip_idYesTineo trip ID (from trips_list).
max_daysNoOptional forecast horizon cap in days. Default 16.

Output Schema

NameRequiredDescriptionDefault
typeNo
citiesNo
detailNo
tripIdNo
outcomeNo
weatherNo
availableCitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile needs no restating. The description does add real behavioral context — daily results are bounded to trip dates and carry confidence tiers, and omitting city_id on a multi-city trip returns the available city IDs rather than failing. It says nothing about caching/staleness or rate limits for an open-world external call, so it is useful but not rich.

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?

Four short sentences, front-loaded with purpose before mode behavior and the trips_list dependency. No filler; the closing note about automatic itinerary weather is the one sentence that could arguably be trimmed, but it carries usage value.

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?

An output schema exists, so return values need not be described, and the description covers the three detail modes, trip scoping and the multi-city edge case. The only gap is how this differs from other weather-related siblings, which is a minor omission for a 5-parameter read tool.

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 every parameter including the hours horizon, detail enum, city_id and max_days cap is already documented in structured form. The description only reinforces the trip_id provenance and the multi-city city_id fallback, adding marginal meaning beyond the schema. Baseline 3 applies when the schema carries the semantics.

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?

Opens with a specific verb+resource ('Get trip weather') and then splits the behavior by mode: daily gives a city-grouped forecast bounded to trip dates with confidence tiers, while current/hourly gives observed or near-term conditions for a single city. That is far more specific than a tautology, though it never contrasts itself with the other weather-adjacent sibling (get_flight_airport_conditions), so sibling differentiation is partial.

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 states a prerequisite ('Provide trip_id from trips_list') and gives a genuine when-not-to-use signal: the itinerary already displays each day's weather and auto-refreshes, implying this tool is for explicit queries. It stops short of naming an alternative tool to use instead for airport or flight weather, so exclusions are implied rather than enumerated.

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