mcp-grounding
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_PLACES_API_KEY | Yes | Google Places API key (Places API New enabled), used by the verify_place tool. |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_placeA | Verifies that a place exists via Google Places Text Search before a destination claim is trusted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| classify_post | Format one Reddit post for classification. The rubric itself is the resource grounding://rubric/v3, because MCP prompt messages have no system role. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Reddit travel-signal classification rubric | The five-label closed taxonomy and its decision tests. Intended to be used as the system prompt. |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possible ambiguity or overlap. The tool's purpose is clearly defined.
The single tool name 'verify_place' follows a clear verb_noun convention, consistent with common MCP naming patterns.
With only one tool, the server is minimal but appropriately scoped for its narrow purpose. It is slightly thin but not excessive.
The server's stated purpose is place verification, and the single tool directly fulfills that purpose with no obvious missing operations.