CatchAll (by NewsCatcher)

Official

by Newscatcher

Overview Schema Source Related Servers Discussions Admin

Python

Remote

assign_webhook_resource

Map a job, monitor, or monitor group to a webhook to trigger notifications for specific deliveries.

Instructions

Map a resource (job, monitor, or monitor_group) to a webhook.

Use when:

You want a webhook to fire for a specific job or monitor's deliveries.

Input Schema

TableJSON Schema

Name	Required	Description
`api_key`	No	CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.
`webhook_id`	Yes	The webhook ID to attach the resource to.
`resource_id`	Yes	The ID of the job/monitor/monitor_group to map.
`resource_type`	Yes	Resource type: 'job', 'monitor', or 'monitor_group'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and description lacks behavioral details like idempotency, overwrite behavior, permission requirements, or limits. Agent may not know if re-mapping replaces or errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short impactful sentences, front-loaded with action and context. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists, description covers core operation. Lacks side-effects or error conditions, but adequate for the simple mapping task.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters. Description mainly restates schema info (e.g., resource types). Adds minimal value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States verb 'map' and clearly specifies resources (job, monitor, monitor_group) to webhook. Distinguishes from sibling tools like create_webhook or list_webhooks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'Use when' clause indicating the scenario. No mention of when not to use or alternatives, but clear enough for common cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server