list_supported_servicesWhich services can be checked.
Lists every supported slug with its human name and status page URL. The list is fixed; arbitrary URLs are not accepted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| services | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral context: the list is fixed, arbitrary URLs are not accepted, and the output contains specific fields. This goes beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, no filler, and the key purpose is front-loaded in the first line. Every sentence adds value: one defines what the tool lists, the other clarifies the fixed nature and rejection of arbitrary URLs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless list endpoint with an output schema and read-only annotations, the description covers what the tool returns, the fixed scope, and a key constraint. Nothing an agent needs to select and call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description correctly indicates that no input is needed and reinforces that only fixed supported slugs are valid, which is relevant for any future parameter expectations.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: listing every supported slug with its human name and status page URL. The phrase 'Which services can be checked' immediately frames the resource and scope, and this differs clearly from the sibling checking tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The opening question establishes the use case: discovering which services can be checked. It does not explicitly name sibling alternatives, but the contrast with check_all_services and check_service_status is implicit and sufficient for a zero-parameter discovery tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: listing supported services, checking one named service, and checking all services at once. Even though check_all_services and check_service_status both check status, the all-vs-one distinction is obvious and reinforced by the descriptions.
All tool names follow a consistent verb_noun pattern: check_all_services, check_service_status, and list_supported_services. The naming clearly indicates both the action and the target, making the set predictable.
Three tools is a well-scoped set for a simple uptime/status-checking server. Each tool serves a distinct and necessary purpose with no redundancy or bloat.
The tool surface fully covers the domain: discovery of supported services, checking a single service, and checking all services. There are no obvious gaps for the stated purpose, and unsupported arbitrary URLs are explicitly disallowed.