Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getUserFromTeam

Retrieve detailed information about a team member using their user ID, so you can identify and manage users within TestingBot.

Instructions

Retrieve detailed information about a specific user in your team by their user ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userId": "<userId>"
    },
    "name": "getUserFromTeam"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesThe user ID

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 supplied, so the description carries the full burden. It does not state whether the call is read-only, what happens if the user ID is not a member of the team, what permission or auth is needed, or what shape the 'detailed information' takes.

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?

One front-loaded sentence with no wasted words. It is efficient, though brevity here comes partly from omitting useful detail rather than from tight editing of rich content.

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?

For a one-parameter read tool with full schema coverage and no output schema, the description is minimally adequate. It leaves out error conditions and any indication of what the returned 'detailed information' contains, which would matter for a lookup tool with no annotations.

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% for the single userId parameter, so the schema already documents it. The description only restates that the lookup is by user ID and adds no format or constraint detail beyond the schema; baseline 3 applies.

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 names a specific verb (retrieve), a specific resource (detailed information about a user), and a scope (in your team, keyed by user ID). It does not differentiate itself from plausible siblings such as getUserInfo or getUsersInTeam, which an agent would need in order to choose correctly.

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 explicit when-to-use guidance and no statement of when not to use it. The phrase 'in your team' hints at scoping, but nothing tells the agent how this differs from getUserInfo or getUsersInTeam, so selection depends on inference.

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