List users
squadcast_list_usersRead-only
List all users in the organization. Squadcast: GET /v3/users.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
squadcast
by io.usefulapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already indicates this is a safe read operation. The description adds only the API endpoint, with no additional behavioral traits such as pagination, permissions, or data volume.
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?
Two short sentences convey the purpose and API endpoint without any wasted words. Efficiently front-loaded.
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?
Given no parameters and the readOnlyHint annotation, the description is fairly complete. It could mention that the list is unfiltered, but the existence of squadcast_get_user for specific users provides implicit contrast.
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?
There are zero parameters, and schema description coverage is 100%. The description adds no parameter info, which is acceptable as no parameters exist.
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 clearly states the tool lists all users in the organization and provides the API endpoint. However, it does not differentiate from the sibling tool squadcast_get_user which retrieves a single user.
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?
No guidance is provided on when to use this tool versus alternatives like squadcast_get_user. The agent is left to infer usage context.
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.