Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Contract Testing: Admin Create User

contract-testing_admin_create_user

Create a new admin user account by providing an email address and display name, with optional fields for personal details and external identity provider configuration.

Instructions

Create a new user account (admin).

Toolset: Admin

Parameters:

  • email (string) required: Email address of the new user

  • name (string) required: Display name of the new user

  • firstName (string): First name

  • lastName (string): Last name

  • externalIdpId (string): External identity provider ID (for SAML/SSO)

  • externalIdpUsername (string): External IdP username (for SAML/SSO)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name of the new user
emailYesEmail address of the new user
lastNameNoLast name
firstNameNoFirst name
externalIdpIdNoExternal identity provider ID (for SAML/SSO)
externalIdpUsernameNoExternal IdP username (for SAML/SSO)
Behavior2/5

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

Annotations are minimal (readOnlyHint false, destructiveHint false). The description adds no behavioral context beyond what annotations provide, such as permission requirements, side effects, or rate limits.

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-loads the purpose. While concise, it could be slightly more structured with a brief usage note.

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?

The description is minimally complete: it states the action and lists all parameters. However, it lacks context about return values (no output schema) and prerequisites for admin use.

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?

Schema description coverage is 100%. The description lists parameters with the same text as the schema, adding no extra meaning or context for any parameter.

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 'Create a new user account (admin)' which uses a specific verb and resource. It distinguishes from sibling tools like contract-testing_admin_update_user and contract-testing_admin_delete_user.

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 explicit guidance on when to use this tool versus alternatives. It only mentions 'Toolset: Admin' but does not state when-not-to-use or suggest other tools for related tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SmartBear/smartbear-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server