Acosta Curated Travel

Search travel articles

search_articles

Read-onlyIdempotent

Keyword search of the Acosta Curated Travel Knowledge Center: destination guides, travel news, entry requirements, and travel tips. Returns up to 10 summaries with links, best match first.

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": {
      "query": "<query>"
    },
    "name": "search_articles"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum results. Defaults to 5.
`query`	Yes	What the traveler wants to read about, e.g. "ETIAS", "river cruise packing", or "paella in Valencia".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-open-world operation, so the safety profile is covered. The description adds genuinely new behavior: result volume, that each result is a summary with a link, and that ordering is by relevance ("best match first"). It does not discuss indexing freshness or what happens when nothing matches, which keeps it from a 5.

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, no filler: scope first, then return behavior. Every clause carries information an agent would otherwise have to guess.

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 usefully characterizes the return value (summaries with links, relevance-ordered, capped at 10). For a simple two-parameter search tool with full annotation and schema coverage, that is nearly everything needed; only the relationship to get_article is left 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 well documented with examples and bounds. The description's "up to 10" restates the schema maximum rather than adding meaning, and it offers no extra guidance on query phrasing beyond the schema's own examples. Baseline 3 applies when the schema carries this load.

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 names a specific verb and resource ("Keyword search of the Acosta Curated Travel Knowledge Center") and lists the covered content types (destination guides, travel news, entry requirements, travel tips), which lets an agent distinguish it from the single-article sibling get_article. It stops short of naming that sibling explicitly, so the differentiation is implicit rather than stated.

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?

"Keyword search" implies the discovery use case, and the content-type list hints at what it covers, but there is no explicit when-to-use guidance and no mention of get_article as the follow-up for retrieving full text. The agent must infer the search-then-fetch workflow.

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

All Acosta Curated Travel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?