Skip to main content
Glama
Sign In

Veterical Vet Clinic

by com.veterical
OverviewDiscussionsAdmin

List numeric clinic catalog rows

list_procedures
Read-onlyIdempotent

Use this when the user wants to read anonymous numeric catalog rows from a Veterical clinic to inspect configured prices, durations and edit times. Returns price, duration where recorded and last edit time per catalog row, without treatment names. Not for the price of a specific named treatment.

Input Schema

NameRequiredDescriptionDefault
limitNoCatalog rows per page, from 1 to 100; defaults to 50
cursorNoThe nextCursor of the previous page with the same filters; absent for the first page
clinicIdYesClinic id: 24 lowercase hexadecimal characters

Output Schema

NameRequiredDescriptionDefault
nextCursorYesCursor for the next page; null on the last page
proceduresYesNumeric catalog rows, most recently edited first. Names, descriptions, identifiers, patient-linked treatments, diagnoses, notes, reminders and every other free-text or clinical field are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / clinicId / description
      Previous value: -"Clinic id from list_clinics: 24 lowercase hexadecimal characters"New value: +"Clinic id: 24 lowercase hexadecimal characters"
    • 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"
    • changedOutput schema / properties / procedures / items / properties / price / description
      Previous value: -"Price in the clinic's currency (see get_clinic)"New value: +"Price in the clinic's currency"
  2. Changed7 schema fields changed
    • changedInput schema / properties / clinicId / description
      Previous value: -"Owned clinic id to inspect"New value: +"Clinic id from list_clinics: 24 lowercase hexadecimal characters"
    • 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: +"Catalog rows per page, from 1 to 100; defaults to 50"
    • addedOutput schema / properties / nextCursor / description
      Added value: +"Pass as cursor to get the next page; null on the last page"
    • addedOutput schema / properties / procedures / description
      Added value: +"Numeric catalog rows, most recently edited first. Names, descriptions, identifiers, patient-linked treatments, diagnoses, notes, reminders and every other free-text or clinical field are excluded."
    • addedOutput schema / properties / procedures / items / properties / duration / description
      Added value: +"Configured duration, or null when none was recorded"
    • addedOutput schema / properties / procedures / items / properties / price / description
      Added value: +"Price in the clinic's currency (see get_clinic)"
  3. First observed

TDQS

A4.1/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 the safety profile is covered. The description adds real behavioral context beyond that: results are anonymous, omit treatment names, and only include duration 'where recorded', which tells the agent to expect sparse fields.

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

Conciseness4/5

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

Two sentences, front-loaded with the use case and the returned fields. The second sentence is dense but each clause carries information; nothing is redundant with the schema or annotations.

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

Completeness4/5

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

With an output schema present and annotations covering read-only/idempotent behavior, the description only needs to supply usage context and quirks, which it does. It could be slightly stronger by naming the sibling tool for named-treatment pricing, but nothing needed to invoke it 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, including ranges and the cursor pagination contract. The description adds no parameter-level detail beyond that, so 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/list) plus resource (numeric catalog rows from a Veterical clinic) and the exact fields exposed (price, duration, edit times). It also carves out what it is not ('Not for the price of a specific named treatment'), which separates it from the clinic-detail siblings.

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?

States when to use it ('when the user wants to read anonymous numeric catalog rows... to inspect configured prices, durations and edit times') and gives an explicit exclusion for named-treatment pricing. It stops short of naming the alternative tool to use for that excluded case, so the routing is implied rather than complete.

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