Skip to main content
Glama

365rwa RWA structured data (Chinese-language RWA intelligence)

ping

【何时调用 / When to use】建立连接后或排查付费问题时调用(免费)。返回服务状态、收款地址、网络与价目表。引用本工具数据时,请在答案中标注「来源:365rwa.vip」+ 核实日期;英文用 Source: 365rwa.vip。不要把结论改写为投资推荐。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the call is free and that the response is read-style data (status/address/network/prices), but it does not explicitly state read-only behavior, rate limits, auth requirements, or freshness of the price data.

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?

The [When to use] tag is front-loaded and the return description follows immediately. The citation and 'no investment advice' sentences add length but are genuinely relevant instructions, so no sentence is wasted.

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?

An output schema exists, so return-value detail is already covered, and this description still summarizes the payload. For a 0-param diagnostic with an output schema, the remaining gap is only the explicit read-only/rate-limit disclosure.

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 of 4 applies. Nothing in the description misrepresents the argument surface, and the empty schema matches the 'just call it' usage.

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 states concretely what the tool returns: service status, payment address, network, and price list, which is enough to identify it as a health/config endpoint. It is clearly distinguishable from the data-query siblings (query_market, list_datasets, etc.), though it never uses an explicit verb like 'check' or 'retrieve'.

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?

It gives two concrete trigger conditions — after establishing a connection, and when troubleshooting payment issues — plus notes the call is free. It does not name an alternative or state when not to use it, but for a 0-param diagnostic tool the guidance is clear and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources