Skip to main content
Glama

findPetsByStatus

Read-onlyIdempotent

Retrieve pets by status—available, pending, or sold—to filter results and find animals matching a specific adoption or inventory state.

Instructions

Finds Pets by status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "<status>"
    },
    "name": "findPetsByStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesStatus values that need to be considered for filteravailable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing beyond the name itself — no note on whether all matching pets are returned, whether results are paginated, or what an empty result implies for an open-world lookup.

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?

A single short sentence with no filler and the essential information front-loaded. It is efficient, though its brevity is partly under-specification rather than disciplined compression.

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 one-parameter, enum-constrained read tool with rich annotations and no output schema, the description is minimally sufficient to invoke correctly. It is not complete enough to tell the agent what a call returns or how to handle the open-world nature of the result.

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 coverage is 100% and the single parameter is a fully documented enum with a default of 'available', so the schema carries the semantics. The description does not explain whether the status filter is an exact match or whether unspecified statuses are included, which would have been marginal added value. 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 gives a specific verb ('Finds') and resource ('Pets') plus a scope indicator ('by status'), which is enough to separate it from a tags-based lookup like findPetsByTags. It stops short of stating what the result set looks like or whether status filtering is exact, so it is clear but not maximally precise.

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

Usage Guidelines2/5

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

There is no guidance on when to prefer this over findPetsByTags or any retrieval-by-id tool, and no mention of prerequisites or expected use cases. The agent must infer from the name alone that this is the list-by-status path rather than a single-pet lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.