Skip to main content
Glama
Sign In
XGR MCP Gateway

XGR MCP Gateway

Official
by xgr-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get XDaLa session detail

get_xdala_session_detail

Retrieve detailed timeline, steps, payloads, and evidence for a specific XDaLa session using owner and session ID.

Instructions

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

NameRequiredDescriptionDefault
ownerYes
sessionIdYes
includePayloadsNo
includeFinalPayloadNo
limitStepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not mention side effects, permissions, rate limits, or error behavior. The description only hints at read-only access by describing retrieval of details, but the agent lacks explicit confirmation of safety.

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 sentence that efficiently communicates the tool's purpose and usage context. No unnecessary words or repetition, and it front-loads the critical 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 the 5 parameters, lack of output schema, and many sibling tools, the description is incomplete. It does not describe the return format, pagination behavior, or effects of optional parameters. The agent lacks enough detail to confidently invoke the tool with appropriate parameters.

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 description coverage is 0%, so the description should explain parameters. It mentions owner and sessionId but does not explain the optional parameters (includePayloads, includeFinalPayload, limitSteps). Their purposes are only weakly implied by the description's mention of 'payloads' and 'steps', leaving ambiguity.

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 description clearly states the tool retrieves details, timeline, steps, payloads, or evidence for a specific XDaLa session, using owner and sessionId. This distinguishes it from sibling tools that list sessions or provide overviews, though it does not explicitly name alternatives.

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 specifies exactly when to use the tool: 'when the user asks for details, timeline, steps, payloads, or evidence for a concrete XDaLa session with owner and sessionId.' It implies that for listing or summary queries, other tools are appropriate, but it does not explicitly state when not to use it or name specific alternatives.

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

Deploy Server

Other Tools