Skip to main content
Glama

Austin Animal Services

Austin Search Animal

austin_search_animal
Read-onlyIdempotent

Look up a specific animal at the Austin Animal Center by its animal ID, name, or breed, across both current intake and outcome records. Use for "what happened to animal A12345" or "is there a [breed] at Austin Animal Center".

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": {
      "breed": "Husky"
    },
    "name": "austin_search_animal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoAnimal name (partial match, case-insensitive), e.g. "Rosie".
breedNoBreed (partial match, case-insensitive), e.g. "Husky", "Pit Bull".
limitNoMax rows per dataset (1-200, default 20).
_apiKeyNoOptional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
animal_idNoExact Austin Animal Center animal ID, e.g. "A12345".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint."New value: +"Optional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the useful fact that results span two datasets (intake and outcome), but says nothing about result shape, whether two result sets come back, or rate-limit behavior aside from what the schema's _apiKey note implies.

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?

Two sentences, front-loaded with the what-and-where, followed by exemplar queries. Every clause carries information an agent can act on; there is no filler.

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?

With zero required parameters and no output schema, the description should say what a no-argument call does and roughly what a result contains; it hints at dual-dataset results but leaves that behavior implicit. Adequate for a simple lookup, but the all-optional parameter set creates a real unanswered question.

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 name, breed, animal_id, limit and _apiKey are already documented with examples and match semantics. The description restates the ID/name/breed lookup modes without adding format or precedence rules (e.g., what happens when breed and animal_id are both supplied), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ("Look up a specific animal at the Austin Animal Center") plus the three lookup keys (ID, name, breed) and the data scope (current intake and outcome records). That scope wording implicitly separates it from aggregate siblings like austin_outcomes_summary and austin_recent_intakes, but no sibling is named explicitly.

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 two concrete usage phrasings ("what happened to animal A12345" and "is there a [breed] at Austin Animal Center") that map directly onto the available parameters. No explicit when-not-to-use or alternative routing is offered, so it stops short of a 5.

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.