Retrieve all available webhook events to identify triggers that make webhooks send notifications, such as test case creation or requirement updates.
Get all webhook events. Retrieve all available webhook events.
Webhook events define the triggers that cause a webhook to send a notification, such as when a test case is created or a requirement is updated.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, open-world, and non-destructive behavior. The description adds domain context (triggers and examples) but omits return format, pagination, and any auth or rate-limit notes.
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 first two sentences are redundant ('Get all webhook events' and 'Retrieve all available webhook events'). The explanatory sentence is useful, but the duplication wastes space.
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 simple zero-parameter read-only collection, the definition is mostly complete. It explains the resource and gives examples, but lacks output shape or pagination info; annotations cover safety.
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?
Zero parameters, so the baseline is 4 per the rubric. There are no parameter semantics to document beyond what the empty schema already communicates.
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?
Specific verb 'Get' and resource 'webhook events', with a clear explanation of what webhook events represent. It does not explicitly contrast with sibling tools like get_webhook_collection or get_webhook, but the resource distinction is clear.
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?
No explicit when-to-use guidance or alternatives; the description only implies it is for listing all webhook events. It does not say when to use this versus get_webhook or get_webhook_collection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.