Veterical Vet Clinic

Count appointments per day

get_clinic_schedule_summary

Read-onlyIdempotent

Use this when the user wants to count scheduled records by UTC day for one Veterical clinic and a bounded date range, including canceled records. Returns appointment counts per UTC day for one clinic, canceled ones included, for the next 7 days by default and at most 31 days; counting stops at 100. Not for seeing individual appointments, pets or owners.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clinicId": "<clinicId>"
    },
    "name": "get_clinic_schedule_summary"
  }
}

Input Schema

Name	Required	Description
`endTime`	No	End of the range as an ISO 8601 date-time, after startTime and at most 31 days later; defaults to 7 days after the start
`clinicId`	Yes	Clinic id: 24 lowercase hexadecimal characters
`startTime`	No	Start of the range as an ISO 8601 date-time; defaults to now

Output Schema

Name	Required	Description
`days`	Yes	One row per UTC day that has appointments, canceled ones included. Aggregate counts only: appointment identifiers and times, animals, owners, diagnoses, treatments, reminders and notes are never returned.
`range`	Yes
`appointmentCount`	Yes
`appointmentCountIsLowerBound`	Yes	True when more than 100 appointments fall in the range

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / clinicId / description

Previous value: -"Clinic id from list_clinics: 24 lowercase hexadecimal characters"New value: +"Clinic id: 24 lowercase hexadecimal characters"

Changed5 schema fields changedSep 27, 2026

changedInput schema / properties / clinicId / description

Previous value: -"Clinic id (24-character lowercase hex)"New value: +"Clinic id from list_clinics: 24 lowercase hexadecimal characters"

changedInput schema / properties / endTime / description

Previous value: -"Range end as ISO 8601; defaults to seven days later"New value: +"End of the range as an ISO 8601 date-time, after startTime and at most 31 days later; defaults to 7 days after the start"

changedInput schema / properties / startTime / description

Previous value: -"Range start as ISO 8601; defaults to now"New value: +"Start of the range as an ISO 8601 date-time; defaults to now"

addedOutput schema / properties / appointmentCountIsLowerBound / description
```
Added value: +"True when more than 100 appointments fall in the range"
```

addedOutput schema / properties / days / description

Added value: +"One row per UTC day that has appointments, canceled ones included. Aggregate counts only: appointment identifiers and times, animals, owners, diagnoses, treatments, reminders and notes are never returned."

First observedSep 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, but the description goes well beyond them: it discloses that canceled records are included in the counts, the default window (7 days) and hard ceiling (31 days), the counting cap of 100, and UTC-day bucketing. Those are exactly the operational facts an agent cannot infer from the annotations.

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?

Two sentences, zero filler, and the trigger condition is front-loaded before the exclusion and the behavioral limits. Every clause (canceled inclusion, defaults, max range, cap, exclusions) carries distinct information.

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?

Despite an output schema existing, the description independently covers purpose, trigger, exclusions, result semantics, defaults, and limits. There is nothing an agent needs in order to call this correctly that is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema omits: the UTC day alignment that governs how startTime/endTime are bucketed, and the 31-day bound combined with a 100-count cutoff on results. This directly informs how an agent should choose the range.

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 (count), resource (scheduled records / appointment counts), and scope (one Veterical clinic, UTC day, bounded range, canceled included). The closing exclusion ('Not for seeing individual appointments, pets or owners') separates it from list_calendar_events and similar siblings without the agent needing to open their schemas.

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?

Opens with an explicit trigger ('Use this when the user wants to count scheduled records by UTC day') and adds a clear when-not clause ruling out per-appointment, pet, and owner lookups. It stops short of naming the alternative tool to use for those cases, so it is not quite a 5.

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?