Trustbase Lab · Trusted Data Infrastructure for the AI Era

Search Policies & Regulations

query_policies

Read-onlyIdempotent

Purpose: search the global rCB regulation library - EU CBAM / EUDR / ESPR / ELV / REACH / ISCC PLUS / PPWR /CSRD, China MIIT waste-tyre rules, solid-waste and circular-economy law, VAT incentives, plus India and Korea EPR and US rules. Guidelines: combine keyword with region and category; set verified=true when the answer must rest on government documents; each hit carries issuing body, policy type, scope, rCB impact, compliance deadline and source link. Limits: policy documents only - no legal advice and no ruling on how a rule applies to a specific company or shipment; B/C-grade entries (media or company statements) are excluded only when verified=true is set. Ex: query_policies(keyword='CBAM'), query_policies(region='中国', category='税收优惠'), query_policies(keyword='ISCC', language='en').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	返回条数上限（默认 20，最大 100）
`region`	No	辖区过滤，如 '欧盟'、'中国'、'印度'、'韩国'、'美国'、'国际'
`keyword`	No	关键词模糊匹配，如 'CBAM'、'增值税'、'ESPR'、'碳'
`category`	No	类别过滤，如 '碳定价'、'循环经济'、'税收优惠'、'认证体系'、'化学品监管'
`language`	No	输出语言	zh
`verified`	No	true=只看 A 级已核实条目
`confidence`	No	置信度：A=政府文件核实, B=企业自述/权威媒体, C=待核实
`response_format`	No	输出格式：markdown=人类阅读, json=Agent 处理友好	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Human-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "text": {
+      "description": "Human-readable result (markdown, or a JSON string when response_format=json).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

First observedSep 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses important behaviors: each hit carries 'issuing body, policy type, scope, rCB impact, compliance deadline and source link,' and B/C-grade entries are 'excluded only when verified=true is set.' It also states output language and response format options, adding value beyond the structured annotations.

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 description is well-structured with Purpose/Guidelines/Limits/Ex sections and front-loads the primary purpose. Each section adds relevant information, though the three example calls in the Ex section are somewhat redundant with the Guidelines and could be trimmed slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters, no required fields, an output schema, and the complexity of a multi-jurisdiction policy search, the description is remarkably complete. It covers what results contain, the verified filtering behavior, language and format choices, permissible use cases, and concrete invocation examples, leaving no major gap for an agent to invoke it correctly.

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 100%, so the schema already documents each parameter. The description adds meaningful usage semantics by advising to combine keyword with region and category, explaining the verified flag's effect on B/C-grade entries, and providing concrete examples like query_policies(keyword='CBAM') that clarify parameter combinations.

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 clearly states a specific verb and resource: 'search the global rCB regulation library' and enumerates the covered frameworks (EU CBAM/EUDR/ESPR, China MIIT, India/Korea EPR, etc.). This distinguishes it from sibling tools like get_policy or get_article by emphasizing a library-wide search over specific documents.

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 description gives explicit guidance: 'combine keyword with region and category' and 'set verified=true when the answer must rest on government documents.' It also provides usage limits, such as 'policy documents only - no legal advice and no ruling on how a rule applies to a specific company or shipment,' though it does not explicitly contrast with sibling tools like get_policy.

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

All Trustbase Lab · Trusted Data Infrastructure for the AI Era tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?