Veterical Vet Clinic

Find a pet owner by name

find_client

Read-onlyIdempotent

Use this when someone names a pet owner of their vet clinic, to get the owner's id before adding an animal or changing their details. Returns up to five owners whose name contains every word given, with id, name and clinic; namesakes are told apart by the last two digits of their phone. Not for finding an animal.

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_client"
  }
}

Input Schema

Name	Required	Description	Default
`search`	Yes	The client'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 clients of this clinic; every clinic of the account when absent

Output Schema

Name	Required	Description
`count`	Yes
`clients`	Yes	The clients 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 clients 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.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description adds useful behavior of its own: a hard cap of five results, the multi-word substring matching rule, and how same-name owners are disambiguated by the last two phone digits. What is missing is the zero-result case and the exact response shape, but with an output schema present that is a minor gap.

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 first, result shape second, exclusion last. Every clause carries information, and the owner-id purpose is front-loaded where an agent will read it before deciding to call.

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?

For a two-parameter lookup with full schema coverage, annotations and an output schema, the description supplies everything the agent needs: when to reach for it, the result cap, and the disambiguation signal. Nothing about invoking it correctly is left unexplained.

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 both parameters are already fully documented, including the word-order/accent-insensitive matching rule and the clinic-scoping default. The description restates the matching rule in compressed form but adds no new syntax, format, or edge-case meaning for either parameter, 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 a pet owner by name") and immediately bounds the scope to the caller's vet clinic. The closing "Not for finding an animal" explicitly separates it from the patient-lookup sibling, so an agent can route without opening either schema.

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 a concrete trigger ("when someone names a pet owner") and the downstream reason ("to get the owner's id before adding an animal or changing their details"), which ties it to create_patient and update_client. It also states the negative case (not for animals), covering when-not-to-use.

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?