tend-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEND_EMAIL | Yes | Your Tend account email | |
| TEND_PASSWORD | Yes | Your Tend account password |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_appointmentsA | List the authenticated patient's upcoming Tend appointments. |
| book_appointmentA | Book an available appointment slot. Requires a slotId — look one up via a slot-search tool once one exists (not yet implemented). |
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 two tools have clearly distinct purposes: one lists appointments and the other books them. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (list_appointments, book_appointment). This is a clean, predictable naming convention.
With only two tools, the server feels minimal for an appointment management context. However, it is not extremely over or under-scoped, so it lands in the borderline category.
The server is severely incomplete: booking requires a slot-search tool that does not exist, and there are no cancel, get, or update operations. This will cause agent failures.