Skip to main content
Glama
SmartBear

SmartBear MCP server

Official
by SmartBear

Contract Testing: Admin Update User

contract-testing_admin_update_user
Read-onlyIdempotent

Update user profile details or change active status. Admin tool for managing SmartBear Contract Testing users.

Instructions

Update a user's profile or active status (admin).

Toolset: Admin

Parameters:

  • userId (string) required: UUID of the user to update

  • active (boolean): Whether the user is active

  • email (string): New email address

  • firstName (string): First name

  • lastName (string): Last name

  • name (string): Display name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name
emailNoNew email address
activeNoWhether the user is active
userIdYesUUID of the user to update
lastNameNoLast name
firstNameNoFirst name
Behavior1/5

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

Description says 'Update' (a write operation) but annotations set readOnlyHint=true. This is a direct contradiction. The description does not disclose any behavioral traits beyond what annotations claim, and the inconsistency severely misleads the agent.

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?

Description is short and front-loaded with the purpose. However, it redundantly lists all parameters which are already in the schema. Could be more concise by omitting the parameter list.

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 description lacks context about side effects, prerequisites, or return values. Given the annotation contradiction, it fails to provide accurate behavioral context. The tool has 6 parameters and no output schema, so more details are needed.

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% and each parameter has a description in the schema. The description repeats these parameter descriptions without adding new semantic context, so it does not add value beyond the schema.

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

Purpose4/5

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

Description clearly states 'Update a user's profile or active status (admin).' Verb and resource are clear, and it distinguishes from create/delete/get siblings by specifying update. However, it does not explicitly contrast with other update tools like update_role or update_team.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies when to use (when updating user profile or active status) but does not provide explicit when-not-to-use guidance or list alternative tools for similar operations.

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