NEXUS AGI

Get entity episodes

get_entity_episodes

Read-onlyIdempotent

List episodes in which the given entity participates, in chronological
order of when they happened (newest first by default).

Args:
    entity_id: UUID of the entity.
    limit: Maximum number of episodes to return (1-200).
    offset: Skip the first N episodes, to page through the rest.
    orden: 'reciente' (newest first, default) or 'antiguo' (oldest first).
    time_range: Window label, same values as in `retrieve_memories`
        ('hoy', 'ayer', 'this_week', 'last_30d', 'all_time', ...).
    since: Inclusive ISO-8601 lower bound, e.g. '2026-08-01' or
        '2026-08-01T14:30:00'. A date without time starts at 00:00.
    until: Inclusive ISO-8601 upper bound. A date without time ends at
        the end of that day.

`time_range` and `since`/`until` are mutually exclusive (422).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity_id": "<entity_id>"
    },
    "name": "get_entity_episodes"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`orden`	No	reciente
`since`	No
`until`	No
`offset`	No
`entity_id`	Yes
`time_range`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 5, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "title": "Offset",
+  "type": "integer"
+}

addedInput schema / properties / orden

Added value: +{
+  "default": "reciente",
+  "title": "Orden",
+  "type": "string"
+}

addedInput schema / properties / since

Added value: +{
+  "default": "",
+  "title": "Since",
+  "type": "string"
+}

addedInput schema / properties / time_range

Added value: +{
+  "default": "",
+  "title": "Time Range",
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "default": "",
+  "title": "Until",
+  "type": "string"
+}

First observedOct 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that: default newest-first ordering, the 1-200 limit bound, pagination via offset, and the 422 error when time_range is combined with since/until.

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?

The summary sentence is front-loaded and the Args block is compact and scannable. The parameter list is somewhat redundant in form but earns its place given the schema has no descriptions at all.

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?

For a read-only listing tool with no output schema, the description covers ordering, paging, filtering, and the mutual-exclusion error. The only gap is that it does not characterize what an episode record contains, which an agent might want before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so for all seven parameters: entity_id as UUID, limit range, offset paging, the 'reciente'/'antiguo' enum values, time_range labels, and ISO-8601 formats with inclusivity and date-only boundary behavior spelled out.

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 first sentence gives a specific verb ('List') and resource ('episodes in which the given entity participates') plus the ordering semantics, which clearly separates it from siblings like get_entity, get_facts_by_entity, or retrieve_memories. It stops short of naming an alternative tool explicitly, so it is clear but not fully sibling-differentiated.

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?

Usage is implied by the entity-scoped framing, and the note that time_range takes the same values as retrieve_memories gives useful cross-tool context. However, there is no explicit statement of when to prefer this over retrieve_memories or get_entity_graph_context, and no when-not guidance.

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

All NEXUS AGI 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.

Resources

Need Help?