Skip to main content
Glama
Sign In

VetClinic.info — Veterinary Specialty Directory

by info.vetclinic
OverviewDiscussionsAdmin

estimate_procedure_cost

Anonymous cost estimate. Returns $low–$high range computed from regional + case factors. Only procedure_slug is required: anything omitted gets a stated default listed in "assumptions" (no zip → the state, else the national range). Deterministic on identical inputs. PII fields are rejected — use quote_for_case for the PII path.

Input Schema

NameRequiredDescriptionDefault
zipNoUS ZIP (5-digit or ZIP+4). Optional.
cityNoCity slug. Optional.
stateNoUS state code or name. Optional; used for the regional adjustment when there is no zip.
case_factorsNoAll optional. Defaults (stated in the result): dog, m, adult, moderate, elective. Plain words and numbers are understood.
procedure_slugYesFrom list_procedures, e.g. tplo-surgery.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changed
    • removedInput schema / properties / case_factors / additionalProperties
      Removed value: -false
    • addedInput schema / properties / case_factors / description
      Added value: +"All optional. Defaults (stated in the result): dog, m, adult, moderate, elective. Plain words and numbers are understood."
    • addedInput schema / properties / case_factors / properties / age_band / description
      Added value: +"puppy, young-adult, adult or senior."
    • removedInput schema / properties / case_factors / properties / age_band / enum
      Removed value: -[
-  "puppy",
-  "young-adult",
-  "adult",
-  "senior"
-]
    • addedInput schema / properties / case_factors / properties / age_band / type
      Added value: +"string"
    • addedInput schema / properties / case_factors / properties / age_years
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / case_factors / properties / comorbidities / description
      Added value: +"cardiac, renal, endocrine, obesity."
    • removedInput schema / properties / case_factors / properties / comorbidities / items / enum
      Removed value: -[
-  "cardiac",
-  "renal",
-  "endocrine",
-  "obesity"
-]
    • addedInput schema / properties / case_factors / properties / comorbidities / items / type
      Added value: +"string"
    • addedInput schema / properties / case_factors / properties / severity / description
      Added value: +"mild, moderate or severe."
    • removedInput schema / properties / case_factors / properties / severity / enum
      Removed value: -[
-  "mild",
-  "moderate",
-  "severe"
-]
    • addedInput schema / properties / case_factors / properties / severity / type
      Added value: +"string"
    • addedInput schema / properties / case_factors / properties / species / description
      Added value: +"dog or cat (canine/feline understood)."
    • removedInput schema / properties / case_factors / properties / species / enum
      Removed value: -[
-  "dog",
-  "cat"
-]
    • addedInput schema / properties / case_factors / properties / species / type
      Added value: +"string"
    • addedInput schema / properties / case_factors / properties / urgency / description
      Added value: +"elective, urgent or emergency."
    • removedInput schema / properties / case_factors / properties / urgency / enum
      Removed value: -[
-  "elective",
-  "urgent",
-  "emergency"
-]
    • addedInput schema / properties / case_factors / properties / urgency / type
      Added value: +"string"
    • addedInput schema / properties / case_factors / properties / weight_band / description
      Added value: +"xs <5 kg · s 5–15 · m 15–30 · l 30–50 · xl >50."
    • removedInput schema / properties / case_factors / properties / weight_band / enum
      Removed value: -[
-  "xs",
-  "s",
-  "m",
-  "l",
-  "xl"
-]
    • addedInput schema / properties / case_factors / properties / weight_band / type
      Added value: +"string"
    • addedInput schema / properties / case_factors / properties / weight_kg
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / case_factors / properties / weight_lb
      Added value: +{
+  "type": "number"
+}
    • removedInput schema / properties / case_factors / required
      Removed value: -[
-  "species",
-  "weight_band",
-  "age_band",
-  "severity",
-  "urgency"
-]
    • addedInput schema / properties / city
      Added value: +{
+  "description": "City slug. Optional.",
+  "type": "string"
+}
    • addedInput schema / properties / procedure_slug / description
      Added value: +"From list_procedures, e.g. tplo-surgery."
    • addedInput schema / properties / state
      Added value: +{
+  "description": "US state code or name. Optional; used for the regional adjustment when there is no zip.",
+  "type": "string"
+}
    • addedInput schema / properties / zip / description
      Added value: +"US ZIP (5-digit or ZIP+4). Optional."
    • removedInput schema / properties / zip / pattern
      Removed value: -"^[0-9]{5}$"
    • changedInput schema / required
      Previous value: -[
-  "procedure_slug",
-  "zip",
-  "case_factors"
-]New value: +[
+  "procedure_slug"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the return shape (low–high range plus an 'assumptions' field), determinism on identical inputs, the defaulting behavior for omitted inputs, and that PII fields are actively rejected. Missing are error semantics for an unknown procedure_slug and confirmation of whether rejected PII fields error or are silently ignored.

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-loaded with the one-line purpose, then behaviors in order of importance (return, requirements, defaults, determinism, exclusions). Every sentence carries information. The 'no zip → the state, else the national range' parenthetical is compressed but readable; no filler sentences.

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 a 5-parameter tool with a nested object, no output schema, and no annotations, the description covers the result shape, defaulting rules, determinism, and the PII exclusion. Gaps are minor: failure behavior for an invalid slug and whether output is paginated/cached are unstated, but nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real semantics beyond it: the fallback chain 'no zip → the state, else the national range' is a resolution order not spelled out in the schema, and it clarifies that required-only is sufficient. It adds value rather than restating field descriptions.

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 ('cost estimate' returning a $low–$high range) and immediately scopes it as anonymous, computed from regional + case factors. This clearly separates it from quote_for_case, which is named as the non-anonymous path. An agent can route correctly without opening any schema.

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?

Explicitly names the alternative and the condition that selects it: 'PII fields are rejected — use quote_for_case for the PII path.' It also clarifies that only procedure_slug is required and what happens to omitted fields. It does not, however, cover its relationship to the other siblings (e.g., when to look up a procedure first vs. just estimating).

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

All VetClinic.info — Veterinary Specialty Directory 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