Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getTeam

Retrieve team plan details, size, and concurrency limits—including running and queued VM or device sessions—before launching many parallel tests.

Instructions

Retrieve team settings: plan details, team size, and concurrency (parallel sessions allowed, running now, and queued waiting for a free slot, for VMs and physical devices). Check this before starting many sessions in parallel.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: "Retrieve" signals a non-mutating read, and it spells out that concurrency is broken into allowed, running, and queued counts across VMs and physical devices. It omits permissions/auth requirements and any rate-limit or caching behavior, which keeps it below a 5.

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?

Two sentences, front-loaded with the payload list and ending with an actionable directive — no filler. The nested parenthetical (allowed / running / queued, for VMs and devices) is information-dense but slightly awkward to parse in one pass.

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 tool with no output schema, the description covers what matters: which fields come back and the specific concurrency dimensions. It never hints at the shape of "plan details" or whether the counts are per-team or per-workspace, a minor residual gap.

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 schema is empty (0 parameters, 100% coverage trivially), so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter tool.

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?

Names a specific verb (Retrieve) and resource (team settings) and enumerates the exact contents: plan details, team size, and concurrency breakdown. That enumerated payload distinguishes it from sibling getters such as getUserFromTeam and getUsersInTeam without needing to name them.

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

Usage Guidelines4/5

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

"Check this before starting many sessions in parallel" gives a concrete when-to-use trigger tied to the concurrency data returned. It stops short of stating when not to call it or naming an alternative, but the trigger is unambiguous.

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