Skip to main content
Glama
Sign In
XGR MCP Gateway

XGR MCP Gateway

Official
by xgr-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get XGR circulating supply

get_xgr_circulating_supply

Retrieve the current circulating supply of XGR tokens from the blockchain.

Instructions

Use this to retrieve circulating supply information exposed by xgr_getCirculatingSupply.

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": "get_xgr_circulating_supply"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It only states it retrieves information from an underlying API call. It does not confirm that it is a safe read operation, mention rate limits, or describe any side effects. For a parameterless read, this is marginal but not misleading.

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, short sentence that is immediately clear and front-loaded. There is no wasted text; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, so the description should hint at the return format. It only says 'circulating supply information' without specifying whether it returns a number, string, or object. For such a simple tool, this is a noticeable gap.

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

Parameters4/5

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

There are zero parameters, and the schema coverage is 100% by default. The description adds no extra parameter information, but since there are none, the baseline of 4 is appropriate as the description does not need to compensate.

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 verb 'retrieve' and the resource 'circulating supply information'. The name and title reinforce this, and the sibling tools contain no alternative for the same data, so it is well-differentiated.

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 explicitly tells the agent to use it for retrieving circulating supply. While it doesn't mention when not to use or list alternatives, given the sibling list, there is no competing tool for this specific data, so the guidance is sufficient.

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