Skip to main content
Glama

Nyc Search Animal

nyc_search_animal
Read-onlyIdempotent

Look up a licensed NYC dog by name (partial match), optionally scoped to a ZIP code. Returns license records from the NYC Dog Licensing Dataset.

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": {
      "name": "Paige"
    },
    "name": "nyc_search_animal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDog name (partial match, case-insensitive), e.g. "Paige".
limitNoMax rows (1-200, default 20).
_apiKeyNoOptional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
zipcodeNoOptional ZIP code filter.

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered by structured data. The description adds that results come from the NYC Dog Licensing Dataset and that matching is partial, but says nothing about row ordering, pagination, or what happens when the partial match is broad. Useful additions exist but are modest.

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 short sentences with zero filler: the lookup behavior and scope come first, the return source second. Nothing is repeated from the title and nothing could be cut without losing information.

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 single-resource lookup with 100% schema coverage and no output schema, this covers what the tool does, how matching works, the optional filter, and the data provenance. The only gap an agent might want is how results are ordered or truncated when the 200-row cap is hit.

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 baseline is 3; every parameter already carries its own description including the limit range and the optional Socrata API key. The description reinforces name and zipcode semantics but adds no format, casing, or limit-behavior detail beyond 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 (look up) and resource (licensed NYC dog) plus the matching behavior (partial name match, optional ZIP scoping) and the data source. An agent can distinguish this from breed- or bite-oriented siblings, though the description never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'by name (partial match), optionally scoped to a ZIP code' — an agent can infer this is the name-lookup route rather than the breed route. There is no explicit when-to-use/when-not statement, no mention of when to prefer nyc_dog_licences_by_breed, and no note on what to do when the name is common.

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.