SiteCheck Crypto & Finance

Sui mainnet current epoch from the public GraphQL API

crypto_sui_move_objects

Read-only

Sui mainnet current epoch from the public GraphQL API: epoch number, reference gas price (MIST per gas unit), epoch start and end time, and total checkpoints. Shared objects and package ids are not included: the public JSON-RPC is deprecated and this tool does not query object lists. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`epoch`	No
`source`	No
`endTime`	No
`checkedAt`	No
`startTime`	No
`totalCheckpoints`	No
`referenceGasPriceMist`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses data provenance (public GraphQL API), the pricing model ($0.002 USDC per successful call via x402 on Base/Solana/Arc), and that failed calls are not charged. That is real added value, but it says nothing about rate limits, freshness/latency, or coverage gaps in the epoch snapshot itself.

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?

Two dense sentences, front-loaded with what is returned, followed by exclusions and then cost. Every clause carries information; the payment-network enumeration (Base, Solana or Arc) is the only mildly expendable detail.

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?

The tool is a simple zero-parameter read with an output schema, so return values need no explanation. The description supplies source, scope boundary, and cost, leaving only freshness/rate-limit behavior unstated, which is a modest gap given the simplicity.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate, and it correctly does not invent parameter advice.

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 names the specific resource (Sui mainnet current epoch) and enumerates the exact fields returned: epoch number, reference gas price in MIST per gas unit, start/end time, total checkpoints. It also preempts the misleading tool name by explicitly excluding shared objects and package ids, which is the main ambiguity an agent would have.

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?

It gives useful negative guidance (does not query object lists; JSON-RPC is deprecated so use this API) but never states positively when an agent should pick this over alternatives, and no sibling tool covers Sui epoch data to route against. Usage is implied rather than prescribed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?