CatchAll

List Entities

list_entities

List your entities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_entities"
  }
}

Input 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

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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 14, 2026

TDQS

C2.8/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 the full burden. It only says 'List' and does not disclose pagination behavior, default page size, filter combination semantics, read-only guarantees, or any side effects. Listing implies read-only, but the description adds no behavioral depth beyond the schema.

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

Conciseness3/5

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

The description is short and free of fluff, making it easy to scan. However, it is nearly a restatement of the title and carries very little information, so it is not an exemplary use of the available space.

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?

With 9 optional parameters Scott, no annotations, and many sibling list tools, the description leaves an agent without enough context about scope, default behavior, or when to choose this tool. The output schema covers return shape, but invocation context is largely missing.

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 every parameter already includes defaults, constraints, and examples. The description itself adds no parameter-level meaning, so the baseline score of 3 is appropriate because the schema does the heavy lifting.

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

Purpose4/5

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

The description states a clear verb ('List') and resource ('your entities'), so an agent knows the basic operation. However, it does not differentiate from sibling tools like list_dataset_entities or list_project_resources, leaving ambiguity about scope.

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?

There is no guidance on when to use this tool versus the many list_* siblings. The single-sentence description provides no context about which listing scenario this applies to, no exclusions, and no alternatives.

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

All CatchAll tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.