CatchAll (by NewsCatcher)

list_entities

List your entities.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number for pagination (default: 1).
`search`	No	Optional text filter on entity name.
`status`	No	Optional status filter: 'pending', 'enriching', 'ready', or 'failed'.
`api_key`	No	CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var.
`sort_by`	No	Optional sort field: 'created_at', 'name', or 'status'.
`page_size`	No	Number of results per page (default: 100, max: 1000).
`project_id`	No	Optional filter to entities belonging to a specific project.
`sort_order`	No	Optional sort direction: 'asc' or 'desc'.
`entity_type`	No	Optional type filter: 'company' or 'person'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 27, 2026

addedInput schema / properties / project_id

Added value: +{
+  "default": "",
+  "description": "Optional filter to entities belonging to a specific project.",
+  "type": "string"
+}

First observedJul 9, 2026

TDQS

C2.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'List your entities' without revealing any behaviors: whether it is read-only, pagination defaults (though schema has defaults), rate limits, or what happens with empty results. The schemas give parameter mechanics but no operational behavior.

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

Conciseness2/5

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

The description is extremely short, but that is not conciseness; it is under-specification. It does not front-load any distinguishing information or context. A single vague sentence provides minimal value, especially when compared to the richer parameter descriptions in the schema.

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

Completeness2/5

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

Given the 9 parameters, a rich output schema, and no annotations, the description should offer more context: e.g., that entities are user-created records, that listing is paginated, or how it relates to dataset entities. The description is incomplete for an agent to fully understand the tool's purpose and behavior without inspecting schemas.

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 description coverage is 100% and each parameter has its own description (page, search, status, api_key, sort_by, page_size, project_id, sort_order, entity_type). The description itself adds no extra meaning beyond the schema, so the baseline of 3 applies. No compensation needed for gaps.

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

Purpose2/5

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

The description says 'List your entities' – a verb and resource, but the term 'entities' is ambiguous in this context. With sibling tools like list_dataset_entities and get_entity, the description does not clarify what distinguishes 'entities' (e.g., all entities vs. those in a dataset). It is a minimal statement that could apply to several tools.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or how it differs from list_dataset_entities, get_entity, or other listing tools. The agent is left to infer usage from the parameter names alone.

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.

Resources

Need Help?