createUsersWithListInput
Creates list of users with given input array. - Creates list of users with given input array.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| x-hapi-auth-state | No | ||
| createUsersWithListInputBody | No |
Petstore MCP Server
by ai.com.mcp
TDQS
D1.8/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden for behavioral disclosure. It merely restates the purpose and gives no information about auth requirements (despite the x-hapi-auth-state parameter), side effects, error handling, or idempotency. This is a significant gap for a bulk creation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short but not concise because it repeats the same phrase twice, providing zero additional value. It could be a single sentence without losing meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with a non-trivial array parameter and no output schema or annotations, this description is grossly incomplete. It lacks return value information, error cases, auth notes, and field descriptions, making it insufficient for an agent to use effectively.
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?
Schema description coverage is 0%, and the description adds no explanation for either parameter. It never mentions the auth state parameter or the structure of the user objects in the array, leaving the agent without critical semantic information.
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 states the verb ('creates') and resource ('list of users'), and the input array differentiates it from createUser. However, the wording is redundant and lacks explicit mention of bulk operation, making it only somewhat clear despite the repetition.
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 alternatives like createUser. It does not mention scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the tool name.
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.