Get service
squadcast_get_serviceRead-only
Get a single service by its id. Squadcast: GET /v3/services/{serviceID}.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| serviceId | Yes | The service id (required). |
squadcast
by io.usefulapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, so the description adds no extra behavioral context. With annotations covering safety, a score of 3 is appropriate.
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 a single sentence that is concise and front-loaded, with no unnecessary words.
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 the simple tool, annotations, and schema, the description is adequate but could mention the return format. No output schema exists, but the tool name implies a service object is returned.
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 coverage is 100% and the description adds no meaning beyond 'by its id'. Baseline 3 applies since schema already describes the parameter.
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 'Get a single service by its id' uses a specific verb and resource, clearly distinguishing it from sibling tools like squadcast_list_services.
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?
The tool is described as retrieving a service by its ID, which implies usage when the ID is known. No explicit when-not or alternatives are given, but context with sibling tools provides clarity.
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.