Cortex

Listcustomeventsforentity

listCustomEventsForEntity

List custom events for an entity with optional filtering by type and time range. Supports pagination and filtering by event type, start time, and end time to retrieve historical event data.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Page number to return, 0-indexed. Default 0.
`type`	No
`context`	Yes	Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your overall objective and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information.
`endTime`	No	If provided, events with less than or equal to timestamp will be returned (UTC, e.g. 2026-06-22T00:00:00)
`tagOrId`	Yes	Entity identifier - can be a tag or CID
`pageSize`	Yes	Number of results to return per page, between 1 and 1000. Default 250.
`startTime`	No	If provided, events with greater than or equal to timestamp will be returned (UTC, e.g. 2026-06-22T00:00:00)
`timestamp`	No	Use 'startTime' instead
`session_id`	Yes	Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 25, 2026

changedInput schema / properties / endTime / description

Previous value: -"If provided, events with less than or equal to timestamp will be returned (a date-time without a time-zone in the ISO-8601 calendar system)"New value: +"If provided, events with less than or equal to timestamp will be returned (UTC, e.g. 2026-06-22T00:00:00)"

addedInput schema / properties / session_id

Added value: +{
+  "description": "Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.",
+  "pattern": "^(start|ses_[0-9A-Za-z]{27})$",
+  "type": "string"
+}

changedInput schema / properties / startTime / description

Previous value: -"If provided, events with greater than or equal to timestamp will be returned (a date-time without a time-zone in the ISO-8601 calendar system)"New value: +"If provided, events with greater than or equal to timestamp will be returned (UTC, e.g. 2026-06-22T00:00:00)"

changedInput schema / required

Previous value: -[
-  "tagOrId",
-  "pageSize",
-  "page",
-  "context"
-]New value: +[
+  "tagOrId",
+  "pageSize",
+  "page",
+  "session_id",
+  "context"
+]

First observedJan 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys a read-only list operation with optional filters, pagination, and historical scope, which is adequate for the basic call, but it does not mention deprecated fields like 'timestamp' or any pagination caveats beyond what the schema already states.

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 front-loaded with the core purpose and is only two sentences, but it redundantly repeats filtering information: 'filtering by type and time range' is restated as 'filtering by event type, start time, and end time'. This repetition costs conciseness.

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?

For a tool with 9 parameters, no output schema, and no annotations, the description gives only basic list-and-filter semantics. It does not describe the return shape, pagination behavior beyond the phrase 'supports pagination', or the deprecated timestamp parameter, leaving several operational gaps for the agent.

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 high (89%), so the schema already documents most parameters. The description adds minor value by clarifying that 'type' means event type and that startTime/endTime form a time range, but it does not compensate for the undocumented 'type' values or describe the deprecated 'timestamp' parameter.

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 clearly states the action ('List') and the resource ('custom events for an entity'), and mentions filtering by type and time range. It is distinct from sibling tools like 'getCustomEventForEntityByUuid' by signaling plural listing rather than single-event retrieval, though it does not explicitly call out that distinction.

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 explicit guidance explains when to use this tool versus related siblings such as 'getCustomEventForEntityByUuid' or 'getCustomDataForEntity'. The phrase 'retrieve historical event data' implies a use case, but there are no alternatives, exclusions, or selection criteria.

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

All Cortex tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?