XGR MCP Gateway

Official

Overview Schema Source Related Servers Discussions Admin

List XDaLa sessions

list_xdala_sessions

Retrieve a paginated list of XDaLa sessions with owner and sessionId pairs, filtered by time window, outcome, and cursor-based pagination for browsing recent sessions.

Instructions

Use this when the user asks to list XDaLa sessions, enumerate recent sessions, or discover owner/sessionId pairs. This returns concrete owner + sessionId pairs and supports keyset pagination. For “last 3 weeks”, pass windowHours=504.

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_xdala_sessions"
  }
}

Input Schema

Name	Required	Description	Default
`owner`	No
`windowHours`	No
`outcome`	No
`limit`	No
`cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It mentions keyset pagination and returning owner+sessionId pairs, but lacks details on response format, error handling, ordering, or default behavior. This is adequate but not thorough for a tool with 5 parameters.

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

Conciseness5/5

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

Two sentences, no wasted words. The first sentence clearly states when to use, the second provides a practical example and mentions pagination. Excellent front-loading of key information.

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?

Given 5 parameters, no output schema, and no annotations, the description is incomplete. It fails to describe cursor usage for pagination, default values, result ordering, or possible outcomes. A list tool with pagination needs more detail to be fully usable.

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

Parameters2/5

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

Schema coverage is 0%, so the description must explain parameters. It only elaborates on windowHours with a usage example. The owner, limit, cursor, and outcome parameters are not described, leaving the agent to infer from the schema alone, which requires regex and nested object comprehension.

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 states the tool's purpose to list XDaLa sessions, enumerate recent sessions, or discover owner/sessionId pairs. It distinguishes from siblings like list_xdala_session_ids (which only return IDs) by specifying it returns concrete owner+sessionId pairs and supports keyset pagination.

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 provides explicit when-to-use guidance ('when the user asks to list XDaLa sessions') and includes a concrete example for windowHours. However, it does not explicitly state when not to use the tool or list alternative tools, though the differentiation from siblings is implied.

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

Deploy Server