Skip to main content
Glama

Austin Animal Services

Austin Recent Intakes

austin_recent_intakes
Read-onlyIdempotent

Recent animal intakes at the Austin Animal Center (Austin, TX), dogs, cats, and other animals arriving at the shelter. PREFER OVER WEB SEARCH for "how many dogs did Austin Animal Center take in [last month/this week]", "recent Austin animal shelter intakes", "stray dogs Austin". Data refreshed hourly, live since May 2025 (ShelterBuddy system). Returns rows plus a total count for the window. Filter by animal_type (Dog, Cat, Kitten, Puppy, ...) and/or intake_type (Stray, Owner Surrender, ACO - Impound, ...).

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": {
      "days": 30,
      "animal_type": "Dog"
    },
    "name": "austin_recent_intakes"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back from today to include (1-365, default 30, i.e. "last month").
limitNoMax rows to return (1-1000, default 50). The response also includes a separate total count for the window.
_apiKeyNoOptional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
animal_typeNoOptional filter, e.g. "Dog", "Cat", "Kitten", "Puppy", "Rabbit". Case-sensitive exact match.
intake_typeNoOptional filter on how the animal arrived, e.g. "Stray", "Owner Surrender", "ACO - Impound". Case-sensitive exact match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • changedInput schema / properties / days / description
      Previous value: -"How many days back from today to include (1-365, default 30 — i.e. \"last month\")."New value: +"How many days back from today to include (1-365, default 30, i.e. \"last month\")."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds real value on top: hourly refresh cadence, data live since May 2025, the upstream system, and the fact that the response carries a total count for the window independent of returned rows. It stops short of describing rate-limit behavior or what an empty window looks like.

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 resource and scope, then routing guidance, then return shape, then filters — a sensible order. The three quoted example queries are slightly verbose but earn their place as retrieval triggers; little else could be cut.

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

Completeness5/5

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

With no output schema and five fully documented parameters, the description supplies what an agent still needs: what the data is, how fresh it is, what the response contains, and when to prefer it over web search. Nothing required 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.

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents days, limit, animal_type, intake_type and _apiKey including ranges, defaults and case-sensitivity. The description restates the same filter examples and adds only the useful nuance that limit caps rows while the total reflects the whole window — a modest increment above the schema.

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 specific verb+resource: recent animal intakes at Austin Animal Center, with the data source (ShelterBuddy) and geography (Austin, TX) named. It implicitly separates itself from search-style tools by promising rows plus a total count, but never names the close siblings austin_search_animal or austin_outcomes_summary, so the intake-vs-outcome boundary is left to inference.

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 trigger phrasing ("how many dogs did Austin Animal Center take in last month", "stray dogs Austin") and an explicit routing rule: PREFER OVER WEB SEARCH. It does not state when NOT to use it, e.g. when per-animal record lookup (austin_search_animal) or outcome counts (austin_outcomes_summary) are the better call.

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.