Schedulia MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| api-key | Yes | API key from schedulia.org used to authenticate the meeting scheduling assistant. | |
| directory | Yes | The absolute path to the schedulia-mcp directory where the server.py is located. |
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 |
|---|---|
| view_meeting_schedulesD | – |
| view_meeting_requestsD | – |
| request_meetingD | – |
| respond_to_meeting_requestD | – |
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 with no overlap: requesting meetings, responding to requests, viewing requests, and viewing schedules. The actions (request, respond, view) and targets (meeting_requests, meeting_schedules) are well-defined, making it easy for an agent to select the correct tool.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., request_meeting, respond_to_meeting_request). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 4 tools, the count is reasonable for a scheduling/meeting domain, covering core actions like request, respond, and view. It might be slightly thin if advanced features (e.g., cancel_meeting, update_schedule) are expected, but it's well-scoped for basic functionality.
The tools cover key aspects of meeting management (requesting, responding, viewing), but there are notable gaps. For example, there's no tool to cancel or modify meetings, and no direct scheduling creation tool, which could limit agent workflows in a full meeting lifecycle.