Skip to main content
Glama

Ask the Global TripX travel helper

ask_tripx
Read-only

Answer a travel question (destination, season, what to pack, entry rules, money, safety, food, airports) using only Global TripX guides, in Korean, English or Japanese. Returns a short answer plus the source pages. Covers 199 countries entry checks and 43,000+ places. Use it for trips from or to Korea and Japan especially.

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": {
      "question": "<question>"
    },
    "name": "ask_tripx"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: ko, en or ja (default: guessed from the question)
questionYesThe traveller question, any language

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 meaningful behavior beyond that: answers are grounded only in Global TripX guides, a short answer is returned alongside source pages, and corpus scale (199 countries, 43,000+ places) is disclosed — useful for judging answer trustworthiness.

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?

Three sentences, front-loaded with the action and topic coverage, followed by return shape and scope. The coverage statistics are mildly promotional but do convey corpus breadth; nothing is redundant enough to cut.

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?

For a two-parameter Q&A tool, the description covers what it answers, the source restriction, the return shape (short answer plus source pages), language support, and coverage scope. With annotations carrying the safety profile and the schema fully documented, nothing essential for correct invocation is missing.

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 coverage is 100%, so both parameters (question and lang enum with default) are already documented, which sets the baseline at 3. The description restates the language options as 'Korean, English or Japanese' but adds no new syntax, default, or interaction detail beyond the schema.

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 ('Answer a travel question') and enumerates the topic space (destination, season, packing, entry rules, money, safety, food, airports) while constraining the answer to Global TripX guides. It does not contrast itself with the sibling 'search_tripx_guides', so an agent must still infer whether to ask or search for guide content.

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?

'Use it for trips from or to Korea and Japan especially' gives a soft geographic usage hint, but there is no explicit when-not guidance and no named alternative such as 'country_entry_check' for entry rules even though entry rules are listed as a supported topic. Usage is implied rather than routed.

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