Skip to main content
Glama

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

list_datasets

【何时调用 / When to use】当用户问「你有哪些 RWA 数据 / 能查什么 / 多少钱」时调用;调用任何付费工具之前也应先调本工具确认数据集、记录数与价格(免费)。引用本工具数据时,请在答案中标注「来源: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": "list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose that the call is free and that it should precede paid queries. It also imposes an output-attribution obligation (source: 365rwa.vip + verification date) and an instruction not to turn conclusions into investment advice, which are behavioral constraints beyond the schema. It does not discuss rate limits or authentication, but for a zero-parameter read-only catalog with an output schema those gaps are minor.

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 guidance is front-loaded in brackets, followed by the free-call rule and citation requirements. The bilingual repetition (Chinese and English) and the citation/advice instructions add length, but each element serves a purpose—routing, pricing transparency, and compliance—so the verbosity is mostly justified.

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?

With no parameters and an existing output schema, the description need not explain return values. It covers purpose, timing, cost, and output-attribution rules. The only missing piece is a brief note on what the dataset list contains (e.g., dataset names and record counts), but that is largely covered by the output schema and the stated 'record count and price' confirmation goal.

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, so the baseline is 4. The description correctly implies no input is needed to discover the catalog, and the empty schema confirms this.

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 makes clear this tool answers what RWA data is available, what can be queried, and at what price — effectively a catalog/dataset listing. It distinguishes itself from the sibling query_* tools by being the free discovery step. It stops short of explicitly saying 'lists all available datasets with record counts and prices' in a single declarative phrase, relying on the quoted user questions to convey scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to call (user asks what data exists / what can be queried / pricing) and gives a strong procedural rule: call this before any paid tool to confirm dataset, record count, and price. This directly routes the agent away from the paid query_* siblings until discovery is done.

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