travel-trends-mcp

get_trip_updates_since

Read-onlyIdempotent

The watched-trip updates log filtered to entries AFTER since.

The notification payload: everything logged for the trip strictly after
the `since` ISO-8601 timestamp (the user's last-seen time), oldest-first.
Returns {trip_id, since, new_update_count, updates}. Use this tool to
fetch the stored update entries the user has not seen yet; for a live
recomputed diff, use whats_changed instead. An empty `since` returns the whole
log. Id is regex-validated (^trip-[a-z0-9-]+$); unknown id ->
{"error": "not_found"}, malformed id -> {"error": "invalid_trip_id"}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	Yes
`trip_id`	Yes

TDQS

A5/5.0

Behavior5/5

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

The description discloses significant behavioral details beyond the annotations: returns entries 'strictly after the `since` timestamp, oldest-first', describes the response shape, and specifies error behaviors for unknown and malformed IDs. Annotations already declare read-only and idempotent, and the description adds no contradictions.

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?

The description is well-structured and concise, leading with the core purpose and then covering notable behaviors and edge cases in a compact, readable form. Every sentence adds value without redundancy.

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?

Even though there is no output schema, the description explicitly states the return object ({trip_id, since, new_update_count, updates}), error responses, and validation rules. Combined with the detailed parameter semantics and usage guidance, the description is fully self-contained for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no descriptions, but the description fully compensates: it defines `since` as 'ISO-8601 timestamp (the user's last-seen time)' and the empty-since behavior, and specifies the `trip_id` format via regex and associated error messages.

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?

The description clearly states the tool's purpose: 'The watched-trip updates log filtered to entries AFTER `since`.' It specifies the resource (trip updates log) and the action (fetch filtered by since), and explicitly distinguishes from the sibling tool whats_changed, which provides a live recomputed diff.

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?

The description provides explicit usage direction: 'Use this tool to fetch the stored update entries the user has not seen yet; for a live recomputed diff, use whats_changed instead.' This states when to use and points to the alternative. It also covers edge cases for empty `since` and validation errors.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All travel-trends-mcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Every tool has a clearly distinct purpose, with explicit cross-references to differentiate overlapping tools (e.g., get_trip_updates_since vs whats_changed, assess_trip vs watch_trip). There is no ambiguity in when to use each tool.

Naming Consistency2/5

Naming is inconsistent: some tools use verb_noun (assess_trip, list_events, watch_trip), some use noun_noun (country_briefing, country_tourism_profile), and one uses a question phrase (whats_changed). This mixed convention reduces predictability.

Tool Count5/5

8 tools is well-scoped for a travel-trends server, covering trip assessment, monitoring, update retrieval, event browsing, daily briefing, and tourism statistics. Each tool earns its place without unnecessary bloat.

Completeness4/5

The core workflows (assess, watch, get updates, explain silence, list events) are well covered. The only notable gap is the absence of trip lifecycle management, such as an unwatch_trip or list_trips tool, which is a minor omission.

Resources

Need Help?