Skip to main content
Glama
Sign In
OpenAPI MCP Gateway

OpenAPI MCP Gateway

by mroops0111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Creates list of users with given input array.

create_users_with_list_input

Create multiple users at once using an input array of user details.

Instructions

Creates list of users with given input array.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_users_with_list_input"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.2
    • removedInput schema / title
      Removed value: -"upstream_callableArguments"
  2. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

The description only states the action ('creates list of users') without disclosing any behavioral details such as required permissions, idempotency, failure modes, or the structure of the input array. With no safety-related annotations (readOnlyHint/destructiveHint), the description carries the full burden but fails to provide meaningful transparency.

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, short sentence with no redundant wording. It is front-loaded and efficient, making it easy to parse, though the brevity comes at the expense of necessary detail.

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?

This tool likely handles batch user creation, yet the schema is empty, there is no output schema, and the description provides only a vague reference to an input array. An agent would have no idea what parameters to pass, how to format the request, or what the response looks like. This is severely inadequate for correct invocation.

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?

The input schema is empty, so the description's mention of a 'given input array' adds a minimal hint that some input is expected. However, it does not explain the array's contents, structure, or format. With schema coverage considered high (vacuously), a baseline of 3 is appropriate, but the description barely compensates for the lack of schema details.

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

Purpose2/5

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

Tautological: description restates name/title.

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 use this tool versus the singular 'create_user' or other user-related operations. No alternatives, prerequisites, or context are mentioned, leaving the agent without any decision support.

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

Deploy Server

Other Tools