Skip to main content
Glama

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

query_issuances

【何时调用 / When to use】当用户问「有哪些真实发行过的 RWA 项目 / 谁发行过代币化债券 / 发行规模多大 / 底层资产是什么」时调用。Use this tool for RWA issuance archives. 返回发行主体/底层资产/规模/监管机构/合作方/日期/官方来源链接,中英双语。可按类别过滤(treasury/credit/stock/bond/fund/commodity/newenergy/realestate/agri)。示例: query_issuances(category='treasury', limit=10)。按次计费 $0.02 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_issuances"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does a lot: it discloses per-call cost ($0.02 USDC), a mandatory attribution format plus verification date, bilingual output, and an explicit prohibition on reframing results as investment advice. Missing only operational traits like pagination behavior or the maximum allowed limit.

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 trigger is front-loaded and the parameter example plus attribution rules follow in a logical order. The bilingual duplication roughly doubles the token count, but each half is purposeful and no sentence is filler; the cost/citation sentences earn their place by changing agent behavior.

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, no annotations, and 0% schema coverage, the description still tells the agent what fields come back, what the call costs, how to filter, and how to cite. Only pagination/limit-ceiling and error behavior are left unaddressed, which is a minor gap rather than a blocker.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: it enumerates all nine valid category values (treasury/credit/stock/bond/fund/commodity/newenergy/realestate/agri) that the schema leaves as a bare string, and demonstrates limit usage via the worked example. It does not explain limit bounds or the default of 20.

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?

The description states a specific verb and resource — querying an RWA *issuance* archive — and enumerates exactly what each record contains (issuer, underlying asset, size, regulator, partners, date, source link). That field list distinguishes it from the sibling query_projects (project profiles) and query_licenses without needing the schemas opened.

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?

The 'when to use' block gives concrete user-question triggers ("which RWA projects actually issued", "who issued tokenized bonds", "how large was the issuance", "what is the underlying asset"). That is clear contextual guidance, but it never names a sibling tool or states when *not* to use this one versus query_projects or 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