OpenAPI MCP Gateway

Finds Pets by status.

find_pets_by_status

Read-onlyIdempotent

Retrieve pets filtered by status (available, pending, sold) from the API. This operation accepts comma-separated statuses to return only matching pet records.

Instructions

Multiple status values can be provided with comma separated strings.

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": "find_pets_by_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes	Status values that need to be considered for filter	available

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.6.2Aug 11, 2026
- addedInput schema / properties / status / default
```
Added value: +"available"
```
- removedInput schema / properties / status / title
```
Removed value: -"Status"
```
- removedInput schema / title
```
Removed value: -"upstream_callableArguments"
```
Changed1 schema field changedv0.5.1Jun 20, 2026
- addedInput schema / properties / status / enum
```
Added value: +[
+  "available",
+  "pending",
+  "sold"
+]
```
First observedv1.0.0Jun 11, 2026

TDQS

A3.5/5.0

Behavior4/5

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

The annotation already declares readOnlyHint, openWorldHint, and idempotentHint, so the agent knows it's a safe read operation. The description adds a behavioral detail that multiple status values can be combined as comma-separated strings, which is not in the annotations. This enriches the agent's understanding of the tool's input behavior.

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?

The description is a single, concise sentence with no fluff or repetition. It is appropriately sized for the tool's simplicity and gets straight to the usage detail. It earns a high score for efficiency.

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 simple one-parameter tool with strong annotations and full schema coverage, the description is mostly adequate. It lacks an explicit return-value statement, but the tool's name and title imply the result is a list of pets. The added comma-separated behavior completes the essential input semantics, making the overall definition reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

The schema describes the status parameter with an enum and a generic description, but the description clarifies that comma-separated multiple values are accepted. This is critical parameter semantics not explicitly stated in the schema. The description adds meaningful value beyond the schema's built-in documentation.

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

Purpose3/5

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

The description only states 'Multiple status values can be provided with comma separated strings,' which does not explicitly state that the tool finds pets. The tool's name and title convey the function, but the description itself lacks a clear verb+resource statement. Thus, the purpose is vague when relying on the description alone.

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?

The description provides no guidance on when to choose this tool over alternatives like find_pets_by_tags. It only offers a parameter formatting note, not tool-selection context. No exclusions or alternative tool references are given.

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