Skip to main content
Glama
Sign In
XGR MCP Gateway

XGR MCP Gateway

Official
by xgr-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List XDaLa session IDs grouped by owner

list_xdala_session_ids

List session IDs from XGR blockchain, grouped by owner, with filters for owner address, time window, and outcome.

Instructions

Use this when the user asks for session IDs. Always returns session IDs grouped by owner because session IDs are only unique together with owner.

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

Input Schema

NameRequiredDescriptionDefault
ownerNo
windowHoursNo
outcomeNo
limitOwnersNo
maxSessionIdsPerOwnerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions the grouping by owner, which is useful, but lacks information on idempotency, side effects, error handling, or return format. Given the absence of annotations, this is insufficient.

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 two concise sentences that directly state the purpose and key behavior (grouping by owner). No unnecessary words, and the important information is front-loaded.

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?

Despite having five optional parameters and no output schema or annotations, the description does not explain the return format, parameter usage, or error conditions. It only covers the grouping behavior, leaving significant gaps for an agent to use the tool correctly.

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

Parameters1/5

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

The schema has 0% description coverage, and the description does not explain any of the five parameters (owner, windowHours, outcome, limitOwners, maxSessionIdsPerOwner). The description adds no meaning beyond the schema, failing to compensate for the coverage gap.

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 verb 'list' and resource 'session IDs' with the grouping by owner, distinguishing it from siblings like 'list_xdala_sessions' which likely returns full session objects. However, it does not explicitly differentiate from similar tools.

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 explicitly says 'Use this when the user asks for session IDs,' providing a clear context for use. However, it does not mention when not to use it or suggest alternatives like 'list_xdala_sessions' for full details.

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