Veterical Vet Clinic

Check Veterical plan and limits

list_subscriptions

Read-onlyIdempotent

Use this when the user wants to read the subscription plan, status, billing frequency and configured capacity limits for a Veterical clinic. Returns plan name, status, billing frequency and plan caps per subscription; caps are limits, not usage. Not for invoices or amounts billed.

Input Schema

Name	Required	Description
`limit`	No	Subscriptions 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
`clinicId`	No	Only this clinic (24 lowercase hexadecimal characters); every clinic when absent

Output Schema

Name	Required	Description	Default
`nextCursor`	Yes	Cursor for the next page; null on the last page
`subscriptions`	Yes	Plan entitlements, newest first. Subscription or customer ids, billed amounts, payment methods, invoices and every processor field are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

removedOutput schema / properties / subscriptions / items / properties / limits / properties / reminders
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```

changedOutput schema / properties / subscriptions / items / properties / limits / required

Previous value: -[
-  "appointments",
-  "patients",
-  "reminders",
-  "seats",
-  "users"
-]New value: +[
+  "appointments",
+  "patients",
+  "seats",
+  "users"
+]

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"

Changed6 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"

addedInput schema / properties / limit / description

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

addedOutput schema / properties / nextCursor / description

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

addedOutput schema / properties / subscriptions / description

Added value: +"Plan entitlements, newest first. Subscription or customer ids, billed amounts, payment methods, invoices and every processor field are excluded."

addedOutput schema / properties / subscriptions / items / properties / limits / description
```
Added value: +"Plan caps, not record counts; null when the subscription carries no cap"
```

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value by clarifying that returned caps are limits rather than usage and by scoping out billing amounts.

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 with no filler: scope and trigger first, exclusions last. Every clause earns its place and nothing is repeated from the schema.

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?

An output schema exists and the schema documents pagination, so the description only needs to establish purpose, usage and the meaning of 'caps' — which it does. An agent has everything required to select and invoke this read-only list tool.

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?

All three parameters (limit, cursor, clinicId) are fully documented in the schema, including pagination semantics and the 24-hex clinic ID pattern. The description adds no parameter-level guidance beyond that, so the baseline 3 applies.

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?

Specific verb ('read') plus resource ('subscription plan, status, billing frequency and configured capacity limits for a Veterical clinic') and an explicit enumeration of returned fields. It is clearly distinguishable from siblings such as list_payments or get_clinic.

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 when-to-use trigger ('when the user wants to read the subscription plan...') and adds a when-not ('Not for invoices or amounts billed'), which steers agents away from billing tools. It stops short of naming the alternative tool explicitly.

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?