List Alert Channels
list_alert_channelsRead-onlyIdempotent
Authenticated tool to list alert channels.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Relin
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds 'Authenticated tool', which is useful but minimal. No further behavioral traits like pagination or rate limits are disclosed.
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?
The description is a single concise sentence with no wasted words. It could benefit from more structure, but it is appropriately sized for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a list tool with no parameters, the description provides basic information (resource and auth). However, it lacks details about return values or how it differs from similar list tools, making it minimally adequate.
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 tool has no parameters, and the description adds no further info. Given the baseline for 0 parameters is 4, and schema coverage is 100%, this score is appropriate.
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 alert channels using a specific verb and resource. However, it does not differentiate from multiple sibling list tools, which could cause confusion.
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 alternative list tools (e.g., list_destinations). The context is implied but lacks explicit usage directions.
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
C2.8/5.0
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between `list_messages`, `list_recent_events`, and `list_message_attempts`, and between `replay_event` and `replay_events`. However, the descriptions generally clarify differences.
Naming Consistency4/5
The naming mostly follows a verb_noun pattern (create_, list_, get_, update_, delete_), with consistent snake_case. A few tools like `rotate_endpoint_secret` and `upsert_event_type` deviate but still use verb_noun structure.
Tool Count2/5
With 52 tools, the set is extremely large and may overwhelm agents. While the domain is complex, this many tools reduce coherence and make selection more difficult.
Completeness4/5
The tool surface is very comprehensive, covering CRUD for most resources, replay, retries, anomaly management, and webhook setup. Minor gaps exist (no delete for destinations, no update for sources), but core workflows are well-supported.