CatchAll (by NewsCatcher)

list_monitors

List all your monitors.

Returns all monitors with their schedule, status, reference query, and webhook config.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number for pagination (default: 1).
`search`	No	Optional text filter on the monitor query.
`api_key`	No	CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.
`ownership`	No	Optional ownership filter: 'all', 'own', or 'shared'.
`page_size`	No	Number of results per page (default: 100, max: 1000).
`project_id`	No	Optional filter to monitors belonging to a specific project.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A3.5/5.0

Behavior2/5

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

No annotations, so description must disclose behavior; it fails to mention pagination (page/page_size params) despite describing as 'all your monitors'. Neither auth requirements nor rate limits are noted.

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, direct sentences with no redundancy; efficient and easy to parse.

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

Completeness3/5

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

Output schema exists, so return format is fine, but the description omits critical context like pagination behavior and default page size, which affects the 'all your monitors' claim.

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?

Input schema covers all 6 parameters with individual descriptions (100% coverage), so the description adds no additional parameter information beyond what schema provides.

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?

Clearly states 'List all your monitors' and enumerates returned fields (schedule, status, etc.), distinguishing from sibling tools like create_monitor, delete_monitor, etc.

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

Usage Guidelines3/5

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

Implies usage for listing all monitors but does not explicitly contrast with get_monitor (single) or list_monitor_jobs, nor provide when-not-to-use guidance.

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

All CatchAll (by NewsCatcher) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool is scoped to a specific resource type and action, with clear distinctions between similarly named operations (e.g., pull_results vs pull_job_csv, initialize_query vs validate_query). No two tools appear to perform the same function.

Naming Consistency4/5

Tools consistently use snake_case verb_noun patterns (create_X, get_X, list_X, update_X, delete_X), with domain-specific verbs like submit, pull, initialize, and validate adding semantic clarity. Minor deviations such as pull_* vs get_* and compound names like create_dataset_from_csv are still predictable.

Tool Count2/5

At 60 tools, the server is heavily overstuffed for a single MCP surface. While the broad domain (datasets, entities, jobs, monitors, projects, webhooks) justifies many operations, the sheer volume exceeds typical recommended limits and includes near-duplicates (pull_results vs pull_job_csv, get_dataset vs get_dataset_status), making agent tool selection unwieldy.

Completeness4/5

The tool set provides robust CRUD and lifecycle coverage for all major resources, including special operations like csv import, webhook mapping, and monitor enable/disable. Minor gaps such as the absence of a get_monitor (single monitor details) and no cancel_job can be worked around via list_monitors and waiting for job completion.

Resources

Need Help?