Skip to main content
Glama
Sign In
sui-mcp-server

sui-mcp-server

by ExpertVagabond
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_coin_metadata

Retrieve coin metadata including name, symbol, decimals, and description by specifying the coin type on the Sui blockchain.

Instructions

Get metadata for a coin type (name, symbol, decimals, description).

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": {
      "coinType": "<coinType>"
    },
    "name": "get_coin_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinTypeYesCoin type (e.g. 0x2::sui::SUI)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description carries burden. Only states it gets metadata; does not disclose side effects, authentication, rate limits, or 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, no waste, front-loaded with purpose.

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 simplicity, description includes return fields (name, symbol, decimals, description) which compensates for lack of output schema. Omits error cases but acceptable.

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 coverage is 100%, so baseline is 3. Description adds no extra meaning beyond schema's description of coinType parameter.

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?

Clearly states it fetches metadata for a coin type, listing specific fields (name, symbol, decimals, description). Distinguishes from siblings like get_balance and get_coins.

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 vs alternatives. Implied by purpose but no exclusions or alternative tool mentions.

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