Skip to main content
Glama

Pet Services Near

pet_services_near
Read-onlyIdempotent

Find veterinary clinics, emergency vets, dog parks, pet stores, or animal shelters near a place, via OpenStreetMap. Answers "emergency vet near Austin TX", "dog parks near me", "pet stores in Denver", "animal shelters near Chicago". Pass a place name (city, address, or landmark), it is geocoded automatically.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "emergency_vet",
      "place": "Austin TX"
    },
    "name": "pet_services_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOne of: vet, emergency_vet, dog_park, pet_store, shelter. Default vet.
limitNoMax results (1-50, default 20).
placeYesPlace name to search near, e.g. "Austin TX", "Portland OR", "downtown Denver".
radius_kmNoSearch radius in kilometres (1-50, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the OpenStreetMap backing and the fact that place strings are geocoded automatically, meaning no coordinates are needed. It says nothing about result ordering, rate limits, or what happens when a place fails to geocode, which is the main remaining gap.

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 capability, then example queries, then the input contract. Slightly redundant in that the example queries and the example place names overlap in purpose, but every sentence is short and functional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read-only lookup with no output schema, the description covers inputs well but never indicates what comes back (names, addresses, distances, opening hours) or how results are ranked. An agent knows how to call it but not what to expect from the response.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the place parameter accepts a city, address, or landmark and is resolved via geocoding, and the kind list is restated in prose matching the schema's allowed values. That extra framing helps an agent construct valid calls.

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 ("Find") plus an enumerated set of resources (veterinary clinics, emergency vets, dog parks, pet stores, animal shelters) and the data source (OpenStreetMap). An agent can immediately tell this is a local-business/POI lookup and distinguish it from the unrelated sibling tools.

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 concrete usage contexts via example queries ("emergency vet near Austin TX", "dog parks in Denver") and explains the input contract: pass a place name and it is geocoded automatically. It does not name exclusions or alternatives, but no sibling in the catalog overlaps with this capability, so the guidance is sufficient in practice.

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.