Skip to main content
Glama
phonhay103

maitabi-mcp-server

by phonhay103

search_tours

Search mountain bus tours and lodge packages using filters for area, dates, price, seats, and stays. Get JSON results with tour pricing, departure dates, and course numbers.

Instructions

Search mountain bus tours and lodge packages on Maitabi (bus.maitabi.jp) with detailed filter criteria.

Returns a JSON string containing matching bus tours, seat options, pricing, departure dates, and course numbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoDeparture day (1-31). Can be a single int, a list of ints, or a string range (e.g., '14-16, 20').
areaNoArea/direction ID (e.g., 18=Tateyama Murodo, 10=Kamikochi, 0=All)
pageNoPage number (1-based)
monthNoDeparture month (1-12)
stay1NoMountain lodge ID for night 1 (e.g., 5=Enzanso, 2=Nishiho Sanso)
stay2NoMountain lodge ID for night 2
stay3NoMountain lodge ID for night 3
styleNoTour style: 1=Round-trip bus, 2=Outbound bus, 3=Inbound bus, 4=Round-trip lodge, 5=Outbound lodge, 6=Overnight day-trip, 7=Taxi plan
keywordNoSearch keyword in Japanese (e.g., '立山', '上高地')
bus_sheetNoBus seat type: 1=Standard, 2=Premium, 3=Outbound Premium / Inbound Standard, 4=Outbound Standard / Inbound Premium, 5=Double seat, 6=Taxi
course_cdNoMaitabi course code (e.g., 'S104C21')
departureNoDeparture point: 1=Tokyo (Takebashi/Shinjuku), 2=Osaka/Kyoto, 3=Nagoya
max_priceNoMaximum price in JPY (e.g., 20000). Filters the results before returning.
min_priceNoMinimum price in JPY (e.g., 10000). Filters the results before returning.
return_dayNoReturn date option: 1=1 day after departure, 2=2 days after, 3=3 days after, 4=4 days after, 5=5 days after
require_available_seatsNoIf True, filters out full/closed tours (満席, 受付終了).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the burden. It mentions the return format (JSON string with specific fields) and the site, but does not disclose pagination behavior, result limits, or any constraints beyond the parameters. It fails to mention that search is read-only (which is likely obvious) but also doesn't discuss potential errors or rate limits. This is a moderate disclosure, but the core behavior is indicated.

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 concise sentences that front-load the resource and action. The description is efficient, with no redundant content, and clearly states the return type.

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?

Given the 100% schema coverage and output schema present, the description is complete for a search tool. It names the domain, the site, and the return content. However, it doesn't specify combination semantics (AND/OR) of filters, which might be valuable, but that's often implied by search filters. So it's adequate.

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?

The schema has 100% coverage with descriptive parameter explanations, so the description adds no additional parameter information. The baseline of 3 applies because the schema does the heavy lifting.

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 searches mountain bus tours and lodge packages on a specific site (Maitabi) and returns a JSON string with tour details. This distinguishes it from sibling search_general_tours which likely handles general tours.

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?

The description implies usage for mountain bus tours and lodge packages but does not explicitly contrast with alternatives like search_general_tours or mention when not to use it. It provides clear context that this is for mountain-specific tours, so an agent can infer when to use it, but no explicit exclusions are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/phonhay103/maitabi-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server