Skip to main content
Glama

Nearest emergency vet

dogpolicies_emergency_vet
Read-onlyIdempotent

Where is the nearest 24-hour or emergency animal hospital to this town, landmark or point: "my dog ate something near Kettleman City", "emergency vet near South Lake Tahoe tonight"? Returns the nearest hospitals with address, phone number, whether they are open 24 hours every day or take emergencies in published hours, the straight-line distance, the hospital's own page and the date it was read. Mountain and desert stretches often have none close: the answer then names the nearest one anyway with its distance. It gives where, when and the phone number only: never medical advice. Tell the traveler to call ahead. Inputs: place as people say it (a city, county, neighborhood, airport) or near={lat, lon}; radius_miles (default 60, up to 200); open_24h_only (default false).

Examples:

  • "My dog ate chocolate, we are near Kettleman City" -> place="Kettleman City"

  • "24-hour vet near South Lake Tahoe" -> place="South Lake Tahoe", open_24h_only=true

  • "Emergency vet near here" -> near={lat:38.68, lon:-119.75}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dogpolicies_emergency_vet"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoA point as an alternative to a town: one of place or near
limitNoHospitals to list
placeNoA city, county, area, region, neighborhood or airport in California or Nevada, e.g. "Monterey", "South Lake Tahoe", "Washoe County, NV", "Las Vegas", "East Bay", "Lake Tahoe", "Central Valley", "Van Nuys", "Koreatown", "Venice Beach", "the Mission", "DTLA", "SFO" or "LAX airport" (an airport searches 5 miles unless radius_miles is given). Accepts the place as people say it; small spelling slips ("Montery") are corrected and the answer says so.
radius_milesNoHow far to look, in miles (straight line)
open_24h_onlyNoOnly hospitals open 24 hours every day
response_formatNo'markdown' for readable text, 'json' for structured datamarkdown

Output Schema

NameRequiredDescriptionDefault
codeNoWith an outcome other than ok: not_found, invalid, unavailable
nextNoCalls that would answer the question, in words
vetsYes
as_ofYesDate the data was built (YYYY-MM-DD)
labelYes
totalYes
caveatYes
centerYes
licenseYes
messageNoWhat happened, in a sentence
nearestNoWhen nothing is inside the radius: the nearest places in the data, with distance_miles
outcomeNoAbsent or ok: a normal answer. no_match: nothing in the data matches, see did_you_mean, nearest and next. bad_input: the arguments cannot be used as given, see next. partial: some of the ids were found, see missing. unavailable: a live source could not be read. None of these is an error.
acceptedNoWith bad_input: each argument that could not be read, with the values it accepts
nearest_24hNoThe nearest 24-hour hospital at any distance, when none is inside the radius
did_you_meanNoClose matches to what was asked for: towns, places, slugs or brands, best first
radius_milesYes
resolved_fromNoSet when a word was read as the value the tool uses: hotel as lodging, NB as north. Each key is the argument; asked is what was sent, used what it was read as
attribution_urlYes
attribution_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds meaningful context beyond that: the fallback when nothing is nearby (it names the closest hospital anyway with its distance) and that small misspellings are silently corrected and disclosed. It does not describe result ordering beyond 'nearest' or what happens when both place and near are supplied.

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?

The answer is front-loaded in the first sentence with scope and return fields, followed by the fallback caveat and the advice boundary, then parameters and examples. It is somewhat repetitive — the quoted user questions in the opening overlap with the example list — but no sentence is wasted.

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 six-parameter read-only geo lookup with an output schema and full annotation coverage, the description covers purpose, returns, fallback behavior and the medical-advice limit. Gaps are minor: no mention of limit/response_format and no explicit comparison to sibling place or policy tools.

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 the schema already documents every parameter including defaults, bounds and the place/near exclusivity rule. The description restates the key defaults (radius 60 up to 200, open_24h_only false) and the colloquial place handling but adds little that isn't already in the schema text, and never mentions limit or response_format.

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?

The description opens with a specific question the tool answers ('Where is the nearest 24-hour or emergency animal hospital') and enumerates the returned fields (address, phone, 24-hour status, straight-line distance, hospital page, date read), so the tool's identity is unmistakable next to siblings like find_hotels or road_conditions.

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?

It gives concrete trigger phrasings ('my dog ate something near X', 'emergency vet near South Lake Tahoe tonight') and an explicit boundary: it supplies where/when/phone only, never medical advice, and the traveler should be told to call ahead. It also explains the place-vs-near choice, though it never routes to a named alternative tool.

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.