XGR MCP Gateway

Get XDaLa session detail

get_xdala_session_detail

Read-onlyIdempotent

Use this when the user asks for details, timeline, steps, payloads, or evidence for a concrete XDaLa session with owner and sessionId.

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": {
      "owner": "<owner>",
      "sessionId": "<sessionId>"
    },
    "name": "get_xdala_session_detail"
  }
}

Input Schema

Name	Required	Description
`owner`	Yes	EVM address of the XDaLa session owner or relevant account.
`sessionId`	Yes	XDaLa session identifier used to query runtime or explorer data.
`limitSteps`	No	Value for the limit steps parameter.
`includePayloads`	No	Value for the include payloads parameter.
`includeFinalPayload`	No	Value for the include final payload parameter.

Output Schema

Name	Required	Description	Default
`data`	Yes	Structured result data returned by the XGR MCP gateway.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and no destructiveness. The description adds no additional behavioral traits (e.g., pagination, caching, authentication) beyond what annotations provide. It does not contradict them.

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?

The description is a single, front-loaded sentence that immediately conveys the use case. Every word is necessary and informative. No wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a detailed query tool with 5 parameters, 100% schema coverage, and an output schema (not shown but present), the description sufficiently sets expectations. It explicitly lists what the tool returns, which is complete given the available metadata.

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 coverage is 100%, with all 5 parameters described inline. The tool description does not add semantic meaning beyond the schema's descriptions (e.g., it does not explain how the parameters affect the results). Baseline 3 is appropriate.

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 verb (get) and resource (XDaLa session detail) and lists specific data retrieved (details, timeline, steps, payloads, evidence). It distinguishes from numerous sibling tools like get_session_status_live or get_latest_session_payload by specifying the level of detail.

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 explicitly gives the use case ('when the user asks for...'), which guides when to invoke. It does not explicitly mention alternatives, but the context of many sibling tools and the specificity of the description make the intended usage clear.

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

All XGR MCP Gateway tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.