Skip to main content
Glama

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

query_regulatory

【何时调用 / When to use】当用户问「RWA 最新监管政策 / 香港(美国/欧盟)有什么新批文 / 哪条法规什么时候生效 / SFC 或 SEC 批了什么」时调用。Use this tool for RWA regulatory approvals. 返回监管机构/类型/获批主体/标题/摘要/日期/官方原文链接,中英双语。可按地区过滤(hk/cn/na/eu/apac/me/global)。示例: query_regulatory(region='hk', limit=5)。按次计费 $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_regulatory"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
regionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description must carry the burden and does add real operational context: per-call pricing ($0.02 USDC), the fields returned (regulator/type/entity/title/summary/date/source link), bilingual output, and a mandatory attribution/non-advice constraint. It omits things like rate limits, pagination, and error behavior, which keeps it below a 5.

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 trigger conditions are front-loaded in the bracketed header and the rest is densely packed with operative detail (return fields, cost, citation rule). A few of the obligations (citation wording, investment-advice disclaimer) are long, but they encode real required behavior rather than filler.

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?

For a two-parameter read tool with no output schema and no annotations, the description is nearly self-sufficient: it explains trigger conditions, region values, return fields, cost, and attribution obligations. Only the lack of pagination/limit bounds and error behavior keeps it from being fully complete.

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 coverage is 0%, so the description must compensate, and it does for `region` by enumerating the allowed codes (hk/cn/na/eu/apac/me/global) that the schema leaves as a bare string. `limit` is only shown via an example value (limit=5) with no bound or default semantics, so one of two parameters remains under-explained.

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 gives a specific verb+resource ('query' + 'regulatory' / 'RWA regulatory approvals') and enumerates the concrete question shapes it answers (new approvals, effective dates, SFC/SEC decisions). It is distinguishable from most siblings by the regulatory-approval framing, though the boundary with query_issuances/query_licenses is only implied rather than stated.

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 explicitly lists the user questions that should trigger the tool and provides a concrete invocation example with region and limit. It does not state when NOT to use it or name the sibling to prefer for adjacent queries (e.g. licenses vs issuances), so it stops short of full routing guidance.

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