getInventory
Returns pet inventories by status. - Returns a map of status codes to quantities.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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?
With no annotations, the description carries full responsibility for behavioral disclosure. It only states the return format (map of status codes) but does not mention auth requirements, side effects, or how the status parameter influences results. The existence of a parameter x-hapi-auth-state is completely undisclosed in behavior terms.
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 very short and front-loaded, stating the verb and resource immediately. It is concise but slightly redundant in repeating 'Returns' twice, and it lacks necessary detail despite being compact.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple but has an unexplained required-but-optional auth parameter. Without an output schema, the description's mention of the map format is helpful but insufficient. The description fails to explain the parameter or provide usage context, leaving the tool incomplete for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter, x-hapi-auth-state, with no description, and the description does not mention it at all. Schema description coverage is 0%, and the description does not compensate by explaining the parameter's purpose or usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns pet inventories by status and specifies the return format as a map of status codes to quantities. This distinguishes it from sibling tools like getPetById and findPetsByStatus.
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 use this tool versus alternatives. It does not mention any prerequisites, exclusions, or contexts where this tool is preferred.
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.