Skip to main content
Glama

Veterinarian license verification from official state open

health_veterinary_license_db
Read-only

Veterinarian license verification from official state open data — Colorado (DORA, VET licenses with degrees and discipline history) and Illinois (IDFPR: licensed veterinarians, controlled-substance licenses, certified veterinary technicians, ever-disciplined flag): license number, name, type, status, issue/renewal/expiry dates, city and discipline details. Search by license number, name or city; active licenses by default. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "state": "<state>"
    },
    "name": "health_veterinary_license_db"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity
limitNoResults, 1 to 100 (default 20)
stateYesCO or IL
offsetNoSkip this many (paging)
lastNameNoLast name (exact, case-insensitive)
firstNameNoFirst name starts with
activeOnlyNotrue (default for name/city searches) = active licenses only
licenseNumberNoState license number

Output Schema

NameRequiredDescriptionDefault
countNo
stateNo
offsetNo
sourceNo
checkedAtNo
licenseesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes meaningfully beyond the readOnlyHint/openWorldHint annotations by disclosing cost ($0.002 per successful call), the payment rail (x402, USDC on Base/Solana and 10 more networks), and that failed calls are not charged — critical for an agent deciding whether to call. It also flags the activeOnly default. It stops short of describing result shape or paging behavior, though an output schema exists.

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?

Front-loads the identity of the tool first, then sources, then search modes, then pricing — a sensible order. The parenthetical field enumeration is dense but informative; little is plainly wasted, though the sentence is long enough to be slightly harder to scan.

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?

For an 8-parameter, two-state lookup with a full schema and output schema, the description covers the essentials an agent needs: which states, what fields come back, how to search, and billing. Missing only minor operational detail such as result caps and paging interaction, which the schema largely covers.

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% with 8 documented parameters, so the schema already carries the semantics. The description only restates the three search axes (license number, name, city) and the active-license default, adding no new detail such as exact-vs-prefix matching or paging limits beyond what the schema states.

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 (veterinarian license verification) and enumerates the exact two sources and their content: Colorado DORA VET licenses with degrees and discipline history, and Illinois IDFPR veterinarians, controlled-substance licenses and CVTs. An agent can distinguish this from the medical/dental board siblings purely from the text.

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

Usage Guidelines3/5

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

'Search by license number, name or city; active licenses by default' gives implied guidance on lookup modes and a default behavior, but there is no statement of when this tool is preferable to a sibling or when it will return nothing (e.g., other states are unsupported). Usage is implied rather than prescribed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources