maitabi-mcp-server

list_district_groups

Fetch mountain area/district groups and tour counts for bus tours, with dynamic filtering based on selected criteria like month, area, style, and more.

Instructions

Fetch mountain area/district groups and tour counts for Maitabi mountain bus tours.

Supports cascading filtering—district groups and counts update dynamically based on other selected filters.

Input Schema

TableJSON Schema

Name	Required	Description
`day`	No	Departure day (1-31)
`area`	No	Area/direction ID (e.g., 18=Tateyama Murodo, 10=Kamikochi, 0=All)
`month`	No	Departure month (1-12). Defaults to current month if omitted.
`stay1`	No	Mountain lodge ID for night 1 (e.g., 5=Enzanso, 2=Nishiho Sanso)
`stay2`	No	Mountain lodge ID for night 2
`stay3`	No	Mountain lodge ID for night 3
`style`	No	Tour 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
`keyword`	No	Search keyword in Japanese (e.g., '立山', '上高地')
`bus_sheet`	No	Bus seat type: 1=Standard, 2=Premium, 3=Outbound Premium / Inbound Standard, 4=Outbound Standard / Inbound Premium, 5=Double seat, 6=Taxi
`course_cd`	No	Maitabi course code (e.g., 'S104C21')
`departure`	No	Departure point: 1=Tokyo (Takebashi/Shinjuku), 2=Osaka/Kyoto, 3=Nagoya
`return_day`	No	Return date option: 1=1 day after departure, 2=2 days after, 3=3 days after, 4=4 days after, 5=5 days after

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.1.10Aug 27, 2026

addedInput schema / properties / area

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Area/direction ID (e.g., 18=Tateyama Murodo, 10=Kamikochi, 0=All)"
+}

addedInput schema / properties / bus_sheet

Added value: +{
+  "anyOf": [
+    {
+      "description": "Bus seat configuration ID for mountain bus tours.",
+      "enum": [
+        1,
+        2,
+        3,
+        4,
+        5,
+        6
+      ],
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Bus seat type: 1=Standard, 2=Premium, 3=Outbound Premium / Inbound Standard, 4=Outbound Standard / Inbound Premium, 5=Double seat, 6=Taxi"
+}

addedInput schema / properties / course_cd

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 50,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Maitabi course code (e.g., 'S104C21')"
+}

addedInput schema / properties / day

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 31,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Departure day (1-31)"
+}

addedInput schema / properties / keyword

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 100,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Search keyword in Japanese (e.g., '立山', '上高地')"
+}

addedInput schema / properties / return_day

Added value: +{
+  "anyOf": [
+    {
+      "description": "Return date option ID for mountain bus tours relative to departure.",
+      "enum": [
+        1,
+        2,
+        3,
+        4,
+        5
+      ],
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Return date option: 1=1 day after departure, 2=2 days after, 3=3 days after, 4=4 days after, 5=5 days after"
+}

addedInput schema / properties / stay1

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Mountain lodge ID for night 1 (e.g., 5=Enzanso, 2=Nishiho Sanso)"
+}

addedInput schema / properties / stay2

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Mountain lodge ID for night 2"
+}

addedInput schema / properties / stay3

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Mountain lodge ID for night 3"
+}

addedInput schema / properties / style

Added value: +{
+  "anyOf": [
+    {
+      "description": "Tour style ID for mountain bus tours.",
+      "enum": [
+        1,
+        2,
+        3,
+        4,
+        5,
+        6,
+        7
+      ],
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Tour 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"
+}

First observedv0.1.1Aug 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds the key behavioral trait that district groups and counts update dynamically based on other selected filters, which is not evident from the schema. This goes beyond a simple fetch description.

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 with zero fluff. The first sentence immediately states the core purpose, and the second adds the cascading behavior. Information is front-loaded and every word earns its place.

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 existence of an output schema, return format is covered. The description states the purpose and a key behavioral nuance. However, it does not address how this tool relates to search_tours or list_filters, which could leave an agent uncertain about when to call it; still, the name and purpose are clear enough for a fetch-style tool.

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 detailed parameter descriptions for all 12 optional parameters. The description adds no additional parameter meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 (Fetch) and resource (mountain area/district groups and tour counts) with clear domain context (Maitabi mountain bus tours). However, it does not explicitly differentiate from sibling tools like list_filters or search_tours, relying on the resource name to imply distinction.

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?

Mentions cascading filtering, which implies use in an interactive filtering context, but does not explicitly state when to use this tool versus alternatives or provide exclusions. The 'when to use' is inferred rather than stated.

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

Deploy Server