testCal
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-eventA | Create a new calendar event. Times must be in ISO 8601 format with UTC timezone (e.g., '2024-12-04T10:00:00Z') |
| search-eventsA | Search for calendar events. Time range must be specified in ISO 8601 format with UTC timezone |
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 2 tools
The tools 'create-event' and 'search-events' have clearly distinct purposes: one creates new events, the other searches existing events. There is no ambiguity between them.
Both tools follow a consistent verb_noun pattern: 'create-event' and 'search-events'. The naming style is uniform and predictable.
With only two tools for a calendar server, the surface is too thin. Typical calendar services require multiple CRUD operations (e.g., update, delete, list) beyond just create and search.
The tool set lacks fundamental operations like updating, deleting, or retrieving a single event by ID. Users cannot manage events beyond creating and searching, which is a significant gap for a calendar service.