Skip to main content
Glama
Sign In

XGR MCP Gateway

by io.github.xgr-network
OverviewDiscussionsAdmin

Get XRC owner summary

get_xrc_owner_summary
Read-onlyIdempotent

Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner.

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>"
    },
    "name": "get_xrc_owner_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesEVM address of the XDaLa session owner or relevant account.

Output Schema

NameRequiredDescriptionDefault
dataYesStructured result data returned by the XGR MCP gateway.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description aligns with these (e.g., 'read-only') but adds context about asset types (XRC-137/XRC-729) and events. No contradiction.

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?

A single 15-word sentence that is front-loaded with the core action and subject. No superfluous information; every word earns its place.

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?

Given the simple input (one parameter) and the presence of an output schema, the description adequately covers the tool's purpose and scope. However, it could mention that the output is aggregated data (summary), but it's not critical.

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?

The only parameter 'owner' is fully described in the schema (pattern and description). The tool description mentions 'for an owner' but does not add new semantic details beyond the schema, so baseline score applies.

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 provides a 'compact read-only summary' of specific resources ('XRC-137/XRC-729 assets and recent XRC events') for an owner, distinguishing it from sibling tools that focus on sessions, transactions, or other data.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for a quick overview, but lacks direct comparisons or conditions for use.

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 toolsInspect
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.

Resources