findPetsByStatus
Finds Pets by status. - Multiple status values can be provided with comma separated strings.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | ||
| x-hapi-auth-state | No |
Petstore MCP Server
by ai.com.mcp
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It only restates 'Finds Pets' and adds the comma-separated behavior, but doesn't disclose return format, error behavior, or authentication requirements.
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?
The description is concise and front-loaded, with two short sentences. The first sentence is somewhat tautological but still clear; the second adds useful parameter detail without waste.
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 simple lookup tool, the description covers the core purpose and status filtering. However, the unexplained optional parameter and lack of return/error details leave gaps, especially without annotations or an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds meaning for the 'status' parameter (comma-separated values), but the schema already provides the enum. The optional 'x-hapi-auth-state' parameter is completely unexplained, and with 0% schema_description_coverage, the description should compensate more.
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 clearly states the tool finds pets by status, which is a specific verb+resource+filter. It distinguishes from sibling 'findPetsByTags' by the status criterion, though it doesn't explicitly name alternatives.
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?
No guidance on when to use this tool versus findPetsByTags or other queries. The comma-separated note is a parameter hint, not a usage guideline.
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.
TDQS
C2.8/5.0
Disambiguation4/5
Most tools target distinct resources and actions, but updatePet and updatePetWithForm overlap in purpose (both update a pet), creating minor ambiguity. Other pairs like createUser and createUsersWithListInput are clearly different.
Naming Consistency3/5
The naming mixes verbs (addPet vs createUser, findPetsByStatus vs getPetById) and styles, but each resource area follows a somewhat predictable pattern (get* for reads, update* for updates, delete* for deletes). Not chaotic, but inconsistent.
Tool Count4/5
19 tools is on the heavier side but reasonable for a petstore server covering pets, orders, and users. Each tool serves a distinct need, and the count reflects the multi-domain scope.
Completeness5/5
The tool surface covers the full lifecycle for pets, orders, and users, including create, read, update, delete, and search operations. Additional operations like login, logout, and inventory are present. No obvious gaps for the expected domain.