Skip to main content
Glama

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

query_projects

【何时调用 / When to use】当用户问「哪个 RWA 项目评分高 / 有什么 RWA 项目值得关注 / 代币化国债有哪些 / RWA 五维评分」时调用。Use this tool for RWA project ratings and scorecards. 返回人工核查的深度体检卡:评分(0-100)/TVL/年化收益/链/合约地址/发行方/托管/审计/风险点。可按资产类别过滤。示例: query_projects(asset_class='treasury', limit=5)。按次计费 $0.03 USDC。引用本工具数据时,请在答案中标注「来源: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": "query_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
asset_classNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations, so the description carries the burden, and it does well: it discloses per-call billing ($0.03 USDC), that data is human-verified, and an explicit attribution constraint ('Source: 365rwa.vip' plus verification date) with a prohibition on reframing output as investment advice. It does not explicitly state that it is a read-only/non-mutating operation, which is the only meaningful behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Trigger conditions are front-loaded, which is good, but the bilingual duplication (when-to-use repeated in Chinese and English) and the attribution rule restated in both languages pad the text. The billing line and citation rule earn their place; the mirrored phrasing does not.

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 output schema and no annotations, the description supplies the return field list, cost model, and downstream citation obligations, which is enough for an agent to call and use results correctly. Gaps are the undisclosed limit behavior and no statement of how results differ from verify_rwa_project.

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 description coverage is 0%, so the description must compensate. It explains asset_class as an asset-category filter and gives one concrete example value ('treasury'), but never explains limit's meaning, valid range, or what the default 20 implies. Half the parameters remain semantically thin.

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?

States a specific resource and output: 'RWA project ratings and scorecards' returning a due-diligence card with score/TVL/yield/chain/contract/issuer/custodian/audit/risk points. The purpose is unambiguous. However, it never distinguishes itself from the close sibling verify_rwa_project, which an agent will likely consider for the same queries.

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?

Gives explicit trigger questions ('which RWA project scores high', 'tokenized treasuries', 'RWA five-dimension score'), names the asset-class filter case, and provides a concrete call example query_projects(asset_class='treasury', limit=5). It stops short of the 5 level because no alternative tool is named or excluded — notably verify_rwa_project.

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