Skip to main content
Glama

Search Global TripX guides

search_tripx_guides
Read-only

Search Global TripX travel guides and tools (destination hubs, trip checklists, weather by month, safety numbers, food, holiday planner, airport tips). Returns titles, one-line summaries and links.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the guides to search: ko, en or ja (default: guessed from the query)
limitNoHow many results to return, 1-10 (default 5)
queryYesWhat to look for, any language (e.g. "Sapporo December packing", "오사카 아이랑", "台湾 SIM")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / lang / description
      Added value: +"Language of the guides to search: ko, en or ja (default: guessed from the query)"
    • addedInput schema / properties / limit / description
      Added value: +"How many results to return, 1-10 (default 5)"
    • addedInput schema / properties / query / description
      Added value: +"What to look for, any language (e.g. \"Sapporo December packing\", \"오사카 아이랑\", \"台湾 SIM\")"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it defines the output shape (titles, one-line summaries, links), which matters because no output schema exists. It omits anything about ranking, result quality, or empty-result behavior.

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 verb and scope, and the parenthetical enumeration earns its space by telling the agent what content is searchable. Slightly list-heavy but not padded.

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?

For a read-only search tool with fully documented parameters, the definition covers scope and return shape, which compensates for the absent output schema. The main remaining gap is routing guidance relative to ask_tripx rather than any missing invocation detail.

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%, with query, lang and limit all documented including examples and a default. The description adds nothing about parameters beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ("Search Global TripX travel guides and tools") and enumerates the covered content types — destination hubs, checklists, weather by month, safety numbers, food, holiday planner, airport tips — so the agent knows the corpus. It does not explicitly contrast with the sibling ask_tripx, leaving that distinction to inference.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the sibling ask_tripx, which is the obvious alternative for a synthesized answer rather than a list of guide links. The use case is only implied by the enumeration of content types.

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