Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

updateUserInfo

Modify a TestingBot user's account details, including first name, last name, and email, to keep profile information accurate and current.

Instructions

Update user account information such as name, email, or other profile details.

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": "updateUserInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail address
lastNameNoLast name
firstNameNoFirst name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation. It does not say whose account is updated (the caller vs. a target user), whether omitted fields are left unchanged, whether the operation is reversible, or what authorization it requires — all material facts for a write tool.

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?

A single well-formed sentence with no wasted words and the core action front-loaded. It is lean, though lean enough to omit useful detail rather than being over-verbose.

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?

For a mutation tool with zero annotations and no output schema, the definition leaves the most important questions unanswered: which user record is targeted, whether all parameters are optional and how a partial update behaves, and what the result looks like. It is under-specified relative to the tool's risk profile.

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%, so email, firstName, and lastName are already documented, and the description adds nothing about format or conflict behavior. Baseline 3 applies since the schema does the heavy lifting.

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?

The description states a specific verb+resource ("Update user account information") and names the fields involved (name, email, profile details), which is clearly distinct from the read-only sibling getUserInfo. It stops short of explicitly saying what it does not do, but the mutation is unambiguous.

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 when-to-use guidance, no indication of prerequisites or permissions, and no mention of how this relates to getUserInfo or team-scoped siblings. An agent must infer entirely on its own when this tool is appropriate.

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