Replay Message
replay_messageAuthenticated tool to replay message.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| appId | Yes | ||
| messageId | Yes |
Relin
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
D1.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are already provided, but the description adds only 'Authenticated', which is a basic behavioral note. It does not disclose effects (e.g., what 'replay' entails, side effects, or durability), leaving significant gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely brief (7 words), but this brevity sacrifices informativeness. It is under-specified rather than concise, lacking critical context that could be added without bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with two required string parameters and no output schema, the description is woefully incomplete. It fails to explain the purpose, behavior, or expected outcome of replaying a message.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description contains no parameter details. Both parameters (appId, messageId) remain undocumented, so the tool fails to add meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description restates the tool name ('replay message') without clarifying the specific verb-resource relationship. It does not distinguish from sibling tools like 'replay_event' or 'replay_events', leading to ambiguity.
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 on when to use this tool versus alternatives. With siblings that perform similar actions (replay_event, replay_events), an agent has no basis to choose correctly.
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.