Veterical Vet Clinic

Find an animal by name

find_patient

Read-onlyIdempotent

Use this when someone names an animal of their vet clinic, to get its id before booking it or changing its details. Returns up to five animals whose name contains every word given, with id, name and clinic; namesakes are told apart by the last two digits of the owner's phone. Not for browsing animals or reading an animal's history, records or vaccinations.

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": {
      "search": "<search>"
    },
    "name": "find_patient"
  }
}

Input Schema

Name	Required	Description	Default
`search`	Yes	The patient's name as the user gave it, or part of it. Every word must appear in the stored name, in any order, ignoring case and accents.
`clinicId`	No	Only patients of this clinic; every clinic of the account when absent

Output Schema

Name	Required	Description
`count`	Yes
`patients`	Yes	The patients whose name matches, with the ids the other tools take. Contact details, dates of birth, notes and clinical records are never returned.
`tooManyMatches`	Yes	More than 5 patients match: none are returned; ask the user for more of the name

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: a hard cap of five results, the fields returned, and the disambiguation rule via the last two digits of the owner's phone. It doesn't say what an agent should do when zero or more than five matches come back.

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 tight sentences: trigger and goal first, expected return shape second, exclusions last. Every clause carries operational information and there is no filler.

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 a full output schema and complete annotations, the description only needs to add behavioral nuance, which it does via the five-result cap and namesake disambiguation. A note on handling zero or ambiguous matches would make it fully self-sufficient for a 2-parameter lookup 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?

Schema coverage is 100%, so both parameters (search, clinicId) are already fully documented with matching semantics and a pattern. The description's 'name contains every word given' largely restates the schema's search description rather than adding new meaning, 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?

States a specific verb and resource ('find an animal by name' / 'get its id') plus the immediate downstream purpose (booking or editing details). It is clearly distinguishable from sibling tools like list_appointments or get_clinic by scoping itself to name-based patient lookup.

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?

Gives a concrete trigger ('when someone names an animal of their vet clinic') and an explicit exclusion ('Not for browsing animals or reading an animal's history, records or vaccinations'). It stops short of naming sibling tools such as find_client or list_procedures as the alternatives for those excluded cases, leaving the routing slightly implicit.

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?