ezyVet MCP Server
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 |
|---|---|
| list_animalsB | Inventory animals on the operator's ezyVet account. Standard read path for triaging cases. |
| get_animalA | Get full metadata for a single animal by id. |
| list_contactsC | Inventory contacts (pet owners + suppliers + staff). |
| list_appointmentsC | List appointments with optional date range filter. |
| create_appointmentA | Create a new appointment on the operator's ezyVet account. Gated by EZYVET_ALLOW_WRITE=true because every created appointment shows up on a real vet's calendar. |
| list_consultsC | Inventory clinical consultation records. |
| list_invoicesD | Inventory invoices. |
| list_productsC | Inventory the product / service catalog billable on invoices. |
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 8 tools
Each tool targets a distinct entity (appointments, animals, consults, contacts, invoices, products) with clear read/write boundaries, so no ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_appointment, list_animals), making the set predictable.
With 8 tools covering core entities in a veterinary practice system, the count is well-scoped and neither sparse nor excessive.
The tool set is read-heavy and lacks update/delete operations for most entities, and only appointments have a create function, leaving significant lifecycle gaps.