Cortex

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 (a date-time without a time-zone in the ISO-8601 calendar system)
`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 (a date-time without a time-zone in the ISO-8601 calendar system)
`timestamp`	No	Use 'startTime' instead

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses pagination and filtering behaviors, but does not mention return shape, ordering, or the deprecated 'timestamp' parameter. Adequate but not rich.

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

Conciseness4/5

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

Two sentences with a clear purpose, but there is redundancy between 'optional filtering by type and time range' and 'filtering by event type, start time, and end time'. Still appropriately sized.

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?

The description covers the core behavior (list, filter, paginate) for an 8-parameter tool with no output schema. It omits required identifier/context parameters and the deprecated timestamp, but the schema fills most gaps.

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 88%, so the schema already documents most parameters. The description maps filtering to type/startTime/endTime and pagination to page/pageSize, adding minimal meaning 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?

The description clearly identifies the tool as listing custom events for an entity, with optional filtering and pagination. It distinguishes from siblings like getCustomEventForEntityByUuid by emphasizing the plural 'events' and historical retrieval.

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?

The description implies usage for retrieving historical event data with filtering and pagination, but does not explicitly exclude alternatives or state when to prefer this over other event tools. The context is clear, but no alternatives are named.

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

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

C2.7/5.0

Disambiguation2/5

Several tools have overlapping or unclear boundaries, notably getEntityDescriptor and listEntityDescriptors share identical descriptions, and getEntityDetails may be confused with them. This ambiguity could easily lead an agent to select the wrong tool for a catalog lookup.

Naming Consistency3/5

Most tools follow a camelCase getXxx/listXxx pattern, but there are clear exceptions like query_docs and get_more_tools that use snake_case, and the verb set includes get, list, query, and search. The mixed conventions are still readable but not fully consistent.

Tool Count2/5

With 31 tools, the surface feels oversized, especially considering the redundant descriptor tools and the meta-tool get_more_tools. The scope is broad but could benefit from splitting into separate servers for catalog, metrics, and other functions.

Completeness2/5

The tool set is almost entirely read-only (get/list/search/query) with no create, update, or delete operations, despite descriptions mentioning 'manage your service catalog'. This leaves significant lifecycle gaps and prevents full catalog management workflows.

Resources

Need Help?