Get team
squadcast_get_teamRead-only
Get a single team by its id. Squadcast: GET /v3/teams/{teamId}.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | The team id (required). |
squadcast
by io.usefulapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds the underlying API endpoint, which is informative but does not disclose additional behavioral traits beyond the read-only nature.
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?
The description is extremely concise with one sentence and an API reference. It front-loads the purpose and contains no unnecessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with one required parameter and no output schema, the description is complete. It clearly identifies the action and input, and the sibling list tool covers the alternative case.
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 parameter 'teamId', with a clear description. The tool description adds no additional parameter semantics beyond what the schema already provides.
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?
The description clearly states 'Get a single team by its id,' which specifies the action and resource. It distinguishes from sibling tools like squadcast_list_teams by targeting a single team via a required ID.
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?
The description implies usage for fetching a single team, but does not explicitly state when to use this tool versus alternatives like squadcast_list_teams. No exclusion or context guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
Each tool targets a distinct resource-action pair, such as incident actions, services, teams, users, schedules, etc. There is no overlap or ambiguity between tools.
Naming Consistency5/5
All tools follow the consistent pattern 'squadcast_verb_noun' in snake_case. Verbs are always first (e.g., acknowledge, add, get, list, resolve), making naming predictable.
Tool Count5/5
With 16 tools, the server covers key incident management operations and supporting resources without being overly numerous or sparse. The scope is well-calibrated.
Completeness4/5
The toolset covers essential incident lifecycle actions (acknowledge, resolve, add notes, list/get incidents) and supporting resources. Minor gaps exist, such as lack of create/update for non-incident entities, but these are not critical for the primary incident response workflow.