Skip to main content
Glama
Sign In

XGR MCP Gateway

by io.github.xgr-network
OverviewDiscussionsAdmin

Get unused XRC-137 rules

get_unused_xrc137_rules
Read-onlyIdempotent

Read-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return.
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

A4/5.0
Behavior4/5

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

Annotations already provide safety hints; description adds specific filter criterion ('no observed tx_receipts usage') and aligns with read-only nature.

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?

Single sentence with key information front-loaded; no extraneous text.

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?

Adequately covers purpose and filter for a read-only list tool; output schema exists to handle return details.

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 covers both parameters with descriptions; description does not add extra semantic value beyond schema.

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 it's a read-only list of owner-specific XRC-137 rules that are unused, distinguishing from siblings like find_reusable_xrc137_rules.

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 usage for checking unused rules but does not explicitly contrast with alternative tools like find_reusable_xrc137_rules or read_xrc137_rule_json.

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