Set an HTTPS URL to receive POST events: application.created, result.submitted, deposit.credited. Empty string disables.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | https:// URL or empty string |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| webhook_url | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "ok": {
+ "type": "boolean"
+ },
+ "webhook_url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "ok"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, openWorldHint, idempotentHint. Description adds that empty string disables the webhook, which is a key behavioral trait not covered by 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 sentences, front-loaded with action ('Set an HTTPS URL...'). No redundant information. Every word earns its place.
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?
Given only one parameter, clear annotations, and existence of an output schema, the description is sufficient. Could mention output details but not required since output schema exists.
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?
Schema coverage is 100% with parameter description 'https:// URL or empty string'. Description adds context: the URL must be HTTPS and the effect of empty string (disables). Adds meaningful info beyond schema.
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?
Description clearly states the tool sets an HTTPS URL for receiving POST events, listing specific event types. This distinguishes it from sibling tools like accept_application or create_task.
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 guidance on when to use vs alternatives. The description implies use for event notifications, but does not state when not to use or mention any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.