Skip to main content
Glama

Austin Animal Services

Austin Outcomes Summary

austin_outcomes_summary
Read-onlyIdempotent

Summary counts of Austin Animal Center outcomes (adopted, transferred, reclaimed, euthanized, etc.) grouped by outcome type, animal type, or month. Use for "how many animals were adopted from Austin Animal Center", "Austin shelter euthanasia rate".

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": {
      "group_by": "outcome_type"
    },
    "name": "austin_outcomes_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoISO date (YYYY-MM-DD), only count outcomes on/after this date. Omit for all available current-system data (since May 2025).
_apiKeyNoOptional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
group_byNoHow to group the counts.

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 / since / description
      Previous value: -"ISO date (YYYY-MM-DD) — only count outcomes on/after this date. Omit for all available current-system data (since May 2025)."New value: +"ISO date (YYYY-MM-DD), only count outcomes on/after this date. Omit for all available current-system data (since May 2025)."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and repeatability are covered. The description adds nothing beyond that about aggregation behavior, rate limits, or data coverage — the 'since May 2025' and API-token rate-limit notes live in the schema, not here.

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?

Two sentences, front-loaded with what the tool returns and followed by usage exemplars; nothing is padding. Slightly more compact would be possible, but the structure is clean.

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?

There is no output schema, yet the description never indicates the shape of a result (e.g. a group key plus a count field), which an agent needs to consume the response. For a simple read-only aggregation with full param coverage this is adequate but not complete.

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 all three parameters (since, _apiKey, group_by) are already documented with formats and enums. The description only echoes the grouping dimension names already present in the group_by enum, adding no new semantics, 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?

The description names a specific verb+resource ('Summary counts of Austin Animal Center outcomes') and enumerates the three grouping dimensions, which is enough to separate it from the sibling lookup tools austin_search_animal and austin_recent_intakes. It never names an alternative explicitly, so it lands at 4 rather than 5.

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?

Two quoted example questions ('how many animals were adopted from Austin Animal Center', 'Austin shelter euthanasia rate') make the intended aggregate-question use case concrete. It gives no when-not-to-use guidance or explicit hand-off to a sibling, so it is clear context without exclusions.

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.