Skip to main content
Glama
Sign In
XGR MCP Gateway

XGR MCP Gateway

Official
by xgr-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get XRC session usage

get_xrc_usage

Fetch usage statistics from Explorer PGRO transaction receipts for XRC-137 rules or XRC-729 OSTC/process filters.

Instructions

Read-only usage statistics from Explorer PGRO tx_receipts for XRC-137 rules or XRC-729 OSTC/process filters.

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": {
      "address": "<address>"
    },
    "name": "get_xrc_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
typeNo
ostcIdNo
ostcHashNo
windowHoursNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

States 'read-only', indicating no mutation. Mentions source and scope, but does not disclose performance, error conditions, or other behavioral traits beyond basic safety. No annotations to supplement.

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

Conciseness4/5

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

Single sentence of 17 words, concise and front-loaded with 'Read-only usage statistics'. However, lacks any parameter explanation, which would be valuable given schema coverage is zero.

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 6 parameters with no schema descriptions, no output schema, and no behavioral details, the description is inadequate. It does not explain return format, filter combination logic, or how to use the parameters effectively.

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?

0% schema description coverage and description adds no meaning to any of the 6 parameters. Agent must rely solely on schema property names and constraints (e.g., address pattern, type enum), which is insufficient.

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?

Description clearly states verb 'get', resource 'usage statistics', source 'Explorer PGRO tx_receipts', and scope 'XRC-137 rules or XRC-729 OSTC/process filters'. It distinguishes from sibling tools like get_xrc_contract or get_xrc_failure_stats.

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?

Implies use when needing usage stats for XRC-137 or XRC-729, but no explicit when-to-use or when-not-to-use compared to many similar sibling tools. Lacks exclusion criteria.

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