list_supported_webhook_shapesList the vendor webhook shapes Relin understands for event identity, ordering, and gap checks.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 indicate read-only, idempotent, and non-destructive behavior. The description adds meaningful context about what the shapes represent (event identity, ordering, gap checks), enhancing transparency.
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?
The description is a single, concise sentence that front-loads the action and purpose without any extraneous information.
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?
The description is complete enough for a simple list tool with no parameters and no output schema. It explains what the list contains and its purpose, though it does not describe the output format.
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?
There are no parameters, so the schema covers 100% of the parameter semantics. The description does not need to add parameter details, and the baseline for no parameters is 4.
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 verb 'List' and the resource 'vendor webhook shapes', along with their purpose for event identity, ordering, and gap checks. It distinguishes itself from sibling list tools by specifying 'vendor webhook shapes'.
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 description does not provide explicit guidance on when to use this tool versus alternatives. While the context is clear for what it does, no usage conditions or exclusions are given.
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.
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.
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.
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.
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.