Skip to main content
Glama

Veterical Vet Clinic

by com.veterical
OverviewDiscussionsAdmin

Check Veterical plan and limits

list_subscriptions
Read-onlyIdempotent

Use this when someone asks which Veterical plan their clinic is on, whether it is active, or how many users, seats, patients or appointments it allows. Returns plan name, status, billing frequency and plan caps per subscription; caps are limits, not usage. Not for invoices or amounts billed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoSubscriptions per page, from 1 to 100; defaults to 20
cursorNoThe nextCursor of the previous page with the same filters; absent for the first page
clinicIdNoOnly this clinic (24 lowercase hexadecimal characters); every clinic when absent

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextCursorYesCursor for the next page; null on the last page
subscriptionsYesPlan 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.

  1. Changed2 schema fields changed
    • 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"
+]
  2. Changed3 schema fields changed
    • 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"
  3. Changed6 schema fields changed
    • 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"
  4. First observed

TDQS

A4.5/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 adds real semantic content beyond that: it enumerates the returned fields and warns that caps are limits rather than usage, which prevents a common misinterpretation. It does not discuss pagination or auth requirements, hence not a 5.

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, front-loaded with the usage trigger, followed by the return contract and the exclusion. Every clause carries distinct information with no repetition of the title or name.

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, so return values need not be spelled out, yet the description still summarizes them usefully. Combined with full parameter coverage, an explicit exclusion, and annotations covering the safety profile, nothing needed to call 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%, so limit, cursor, and clinicId are fully documented in the schema itself. The description adds no syntax, default, or format detail beyond the schema, which matches the baseline 3 for a schema that does the heavy lifting.

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+resource (list subscriptions) and immediately narrows the intent to plan, status, and plan caps. It also explicitly disambiguates from the closest sibling, list_payments, by ruling out invoices and billed amounts.

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

Usage Guidelines5/5

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

Gives concrete trigger phrasing ('when someone asks which Veterical plan their clinic is on, whether it is active, or how many users, seats, patients or appointments it allows') and an explicit exclusion that reroutes to the billing sibling. Both when-to-use and when-not-to-use are present.

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 toolsInspect
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