NEXUS AGI

List entities

list_entities

Read-onlyIdempotent

List entities with pagination, optionally limited to those created within a time window.

With a window, results are filtered by creation time and ordered newest
first; without one, the order is unspecified.

Args:
    page: Page number (1-based).
    size: Items per page (1-1000).
    time_range: Named window, same vocabulary as retrieve_memories (for
        example 'esta_semana', 'last_30d').
    since: ISO 8601 start of the window (for example '2026-08-01').
    until: ISO 8601 end of the window; a date without a time covers the
        whole day.

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	Default
`page`	No
`size`	No
`since`	No
`until`	No
`time_range`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely new behavioral context: results are ordered newest-first only when a time window is supplied, otherwise order is unspecified. That ordering caveat is not derivable from annotations or schema.

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?

Purpose and the ordering rule are front-loaded, and the Args block is a clean, scannable list with no filler. Slightly long for a simple list tool, but every line carries information.

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?

With no output schema, a 0%-described schema, and no annotations on ordering/filtering, the description supplies the operationally important facts (pagination, window filtering, ordering) so an agent can call it correctly. It omits what an entity record contains, but that is outside the calling contract.

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

Parameters4/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 largely does: it defines page (1-based), size (1-1000), time_range as a named window with examples, since/until as ISO 8601, and the whole-day behavior of a bare date. The only weakness is that time_range's vocabulary is defined only by reference to retrieve_memories, which the agent may not have loaded.

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?

States a specific verb and resource ("List entities") plus the pagination scope and optional time-window filter, so the agent knows exactly what it returns. It does not, however, name the sibling it differs from (search_entities would be the natural alternative), leaving differentiation implicit.

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?

The description explains the two modes (with/without a window) and their ordering consequences, implying when each is useful, but never states when to prefer this over search_entities or get_entity. Usage is inferred rather than directed.

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?