rollin-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROLLIN_API_KEY | No | Your ROLLIN API key for unlimited requests (optional; trial mode works without it). |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_locationsA | Search for wheelchair-accessible restaurants, cafes, and bars near a location. Returns scored results with accessibility features. Requires latitude and longitude. |
| get_location_detailsA | Get full accessibility details and score breakdown for a specific location. Returns features, score components, and verification status. |
| list_regionsA | List all regions where accessibility data is available. Returns states, regions, and location counts for each area. |
| submit_feedbackA | Submit a correction or feedback about a location's accessibility. Use this when a user reports that accessibility information is inaccurate. |
| check_healthA | Check if the ROLLIN API is operational. Also reports trial mode status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api-info | ROLLIN API overview and available features |
TDQS
Scored across 5 tools
Each tool serves a unique purpose: health check, location details, region listing, location search, and feedback submission. No two tools have overlapping functionality, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., check_health, list_regions). The verbs are distinct and descriptive, and the naming is uniform throughout.
With 5 tools, the server is tightly scoped to its purpose of providing wheelchair accessibility information. Each tool is essential for the core workflows, and the count is neither too few nor too many.
The tool set covers key operations: health check, region discovery, location search, detail retrieval, and feedback. A minor gap is the lack of a tool to list all locations within a region without specifying coordinates, but the core functionality is well-covered.