local-events-mcp
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 |
|---|---|
| list_sourcesB | List sources with functional status and scraper health. |
| list_events_by_source_and_dateC | Return a source's events for one day, including the scraper status. |
| scraper_is_validC | Check whether a source-specific scraper is still returning semantic data. |
| get_events_for_time_periodC | Return semantic events for a source within the next N days. |
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 4 tools
Each tool has a clearly distinct purpose: get events for a time period, list events for a specific day with scraper info, list sources, and check scraper validity. No overlap in functionality.
Most tools use a consistent verb_noun pattern in snake_case (get_events, list_events, list_sources), but 'scraper_is_valid' deviates with an adjective instead of a verb, breaking the pattern slightly.
4 tools is well-scoped for a local events MCP server. Each tool serves a clear purpose without redundancy, and the count is appropriate for the domain.
The tool surface covers basic querying of events and source/scraper status but lacks CRUD operations for events and sources (e.g., add source, update event). Notable gaps exist for managing data.