Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Contract Testing: Admin Create User

contract-testing_admin_create_user
Read-onlyIdempotent

Creates a new admin user account in SmartBear's contract testing platform, requiring email and display name.

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)
Behavior1/5

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

The description states 'Create' (a mutation), but annotations include readOnlyHint: true, directly contradicting the description. This misleads the AI agent about the tool's safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description includes redundant 'Toolset: Admin' and a parameter list that mirrors the schema. It is somewhat concise but could be better structured with front-loaded usage hints.

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?

Despite having annotations, the contradiction undermines completeness. No output schema is present, and the description does not explain return values, side effects, or authentication requirements, leaving gaps for a create operation.

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 coverage is 100%, so the input schema already documents all parameters. The description simply repeats parameter names and types without adding new semantics or usage guidance, meeting baseline expectations.

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 'Create a new user account (admin)' uses a specific verb and resource, clearly distinguishing it from sibling tools like contract-testing_admin_delete_user or contract-testing_admin_get_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?

No guidance on when to use this tool versus alternatives, such as contract-testing_admin_invite_users or contract-testing_admin_create_system_account. Lacks context on prerequisites or scenarios.

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