Veterical Vet Clinic

List closures, holidays and blocked time

list_calendar_events

Read-onlyIdempotent

Use this when the user wants to list non-appointment calendar blocks and additional opening periods for a Veterical clinic. Returns each block or extra opening with start, end, all-day flag, scope (clinic, staff or room) and type, without titles, notes or names. Not for appointments.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Blocks per page, from 1 to 100; defaults to 20
`cursor`	No	The nextCursor of the previous page with the same filters; absent for the first page
`endTime`	No	Only blocks ending before this ISO 8601 date-time
`clinicId`	No	Only this clinic (24 lowercase hexadecimal characters); every clinic when absent
`startTime`	No	Only blocks starting at or after this ISO 8601 date-time

Output Schema

TableJSON Schema

Name	Required	Description	Default
`nextCursor`	Yes	Cursor for the next page; null on the last page
`calendarEvents`	Yes	Non-appointment calendar blocks, earliest first. Event identifiers, clinic or staff references, titles, notes, owner or animal linkage and clinical fields are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

changedInput schema / properties / clinicId / description

Previous value: -"Only this clinic (id from list_clinics, 24 lowercase hexadecimal characters); omit for every clinic"New value: +"Only this clinic (24 lowercase hexadecimal characters); every clinic when absent"

changedInput schema / properties / cursor / description

Previous value: -"nextCursor from the previous page with the same filters; omit for the first page"New value: +"The nextCursor of the previous page with the same filters; absent for the first page"

changedOutput schema / properties / nextCursor / description

Previous value: -"Pass as cursor to get the next page; null on the last page"New value: +"Cursor for the next page; null on the last page"

Changed10 schema fields changedSep 27, 2026

changedInput schema / properties / clinicId / description

Previous value: -"Filter by owned clinic id"New value: +"Only this clinic (id from list_clinics, 24 lowercase hexadecimal characters); omit for every clinic"

changedInput schema / properties / cursor / description

Previous value: -"Opaque cursor from a prior result"New value: +"nextCursor from the previous page with the same filters; omit for the first page"

changedInput schema / properties / endTime / description

Previous value: -"Only blocks ending before this ISO 8601 time"New value: +"Only blocks ending before this ISO 8601 date-time"

addedInput schema / properties / limit / description

Added value: +"Blocks per page, from 1 to 100; defaults to 20"

changedInput schema / properties / startTime / description

Previous value: -"Only blocks starting at or after this ISO 8601 time"New value: +"Only blocks starting at or after this ISO 8601 date-time"

addedOutput schema / properties / calendarEvents / description

Added value: +"Non-appointment calendar blocks, earliest first. Event identifiers, clinic or staff references, titles, notes, owner or animal linkage and clinical fields are never returned."

addedOutput schema / properties / calendarEvents / items / properties / effect / description
```
Added value: +"BLOCK removes bookable time; OPEN adds hours on a normally closed time"
```
addedOutput schema / properties / calendarEvents / items / properties / scope / description
```
Added value: +"CLINIC: the whole clinic; PROVIDER: one or more staff; SEAT: one room"
```

addedOutput schema / properties / calendarEvents / items / properties / type / description

Added value: +"Label such as COURSE, MEETING, VACATION, SICK, HOLIDAY, MAINTENANCE or OTHER"

addedOutput schema / properties / nextCursor / description

Added value: +"Pass as cursor to get the next page; null on the last page"

First observedSep 25, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still earns credit by disclosing the actual payload shape (start, end, all-day flag, scope, type) and, importantly, what is deliberately omitted ('without titles, notes or names') — a non-obvious output constraint the agent cannot infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the usage condition, then the returned fields, then the exclusion. Every sentence carries distinct information with no repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers when to call, what is returned, what is omitted, and what the tool is not for. An output schema exists so return values need not be elaborated, yet the description still summarizes them usefully. Nothing needed to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with limit, cursor, startTime, endTime and clinicId all documented in the schema itself, so the baseline is 3. The description mentions scope values (clinic, staff, room) but adds no filtering syntax or format detail beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('list') and a precisely scoped resource ('non-appointment calendar blocks and additional opening periods'), and explicitly carves out what it is not ('Not for appointments'). An agent can distinguish this from appointment-related siblings without reading the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening clause gives a clear triggering condition ('when the user wants to list non-appointment calendar blocks') and the closing sentence provides an explicit exclusion ('Not for appointments'). It stops short of naming which sibling to use instead for appointments or availability, so it is strong context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Veterical Vet Clinic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?