Tabelog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| suggest_searchC | Autocomplete restaurants, areas and genres for a keyword. |
| search_restaurantsB | Search Japanese restaurants. search_type is normal, current or map; area_datatype is area1, area2, majorCity, municipal, prefecture or station; genre_datatype is genre0 to genre3; sort_mode is totalRanking, distance, accessRanking, reservationRanking or domesticMostReserved. Get ids from the area tools and suggest_search. |
| restaurant_detailC | Get details for one restaurant. |
| restaurant_reviewsC | Get reviews for a restaurant. |
| restaurant_menuC | Get a restaurant's menu list. |
| restaurant_photosC | Get a restaurant's photos. |
| restaurant_vacancyC | Get vacancy status for a restaurant over the next few days. |
| popular_nearbyC | Get popular items near a coordinate. |
| area_level1C | List first level areas for a prefecture. |
| area_level2C | List second level areas inside a first level area. |
| stationsC | List stations in a second level area. |
| tabelog_getB | Read-only escape hatch: GET any endpoint name under /tabelog_inbound_appli/ from the Tabelog spec (see tabelog-api-spec). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes: restaurant detail vs reviews/menu/photos/vacancy, hierarchical area tools, and search/autocomplete. The only overlap is tabelog_get, which can reach any GET endpoint and could compete with dedicated tools, but it is explicitly framed as an escape hatch.
The names use several conventions: verb_noun (search_restaurants, suggest_search), resource_noun (restaurant_reviews), noun_detail (restaurant_detail), area_level1/2, and bare nouns like stations. They remain readable, but the pattern is not predictable.
12 tools is well-scoped for a restaurant discovery/detail server. Each tool maps to a meaningful step: location resolution, search/autocomplete, restaurant details, subresources, nearby popularity, and a generic read escape hatch.
The surface covers area hierarchy, stations, autocomplete, search, restaurant detail, reviews, menu, photos, vacancy, and nearby popularity. Minor gaps include an explicit genre taxonomy listing and reservation/booking actions, but the read-only escape hatch mitigates missing GET coverage.