Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getUsersInTeam

Retrieve a list of all users in your team, including their roles and permissions, to review access and manage team membership.

Instructions

Get a list of all users in your team with their roles and permissions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/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 disclose the shape of the returned data (users with roles and permissions) and the read-only nature implied by "Get." It says nothing about pagination, team scoping/auth requirements, rate limits, or what happens with large teams.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the resource and the returned fields are both stated up front.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read with no output schema, the description covers what the tool returns (users, roles, permissions), which is the main thing an agent needs. Only secondary operational details like pagination or result size limits are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no schema meaning to supplement; baseline is 4. The description correctly signals that the call is unfiltered and scoped entirely by the caller's team context.

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?

States a specific verb and resource ("Get a list of all users in your team") and adds the payload contents (roles and permissions). It implicitly separates itself from the singular getUserFromTeam and getTeam, though it never names those siblings explicitly.

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?

Usage is implied by "all users in your team," which suggests a bulk roster lookup rather than a single-member query. There is no explicit when-to-use, when-not-to-use, or pointer to getUserFromTeam for single-user lookups.

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