Skip to main content
Glama

Trustbase Lab · rCB & Chemical Recycling Data

by com.trustbaselab
OverviewDiscussionsAdmin

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 KoreaEPR and US rules. Guidelines: combine keyword with region and category; set verified=true when the answer mustrest on government documents; each hit carries issuing body, policy type, scope, rCB impact, compliance deadlineand source link. Limits: policy documents only - no legal advice and no ruling on how a rule applies to aspecific company or shipment; B/C-grade entries (media or company statements) are excluded only whenverified=true is set. Ex: query_policies(keyword='CBAM'), query_policies(region='中国', category='税收优惠'),query_policies(keyword='ISCC', language='en').

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesHuman-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond annotations: verified=true excludes B/C-grade entries, each hit carries issuing body/policy type/scope/rCB impact/deadline/source link, and results are limited to policy documents only. This gives the agent a clear sense of what will be returned and what is excluded.

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 organized into Purpose, Guidelines, Limits, and Examples, making it easy to scan. It is fairly long but every section adds value for an 8-parameter search tool. Minor formatting issues like 'PPWR /CSRD' aside, it remains front-loaded and well-structured.

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 the high parameter count, existing output schema, and rich sibling context, the description covers the essential aspects: what the tool searches, how to combine filters, when to require verified results, what each result contains, and clear usage examples. The limits section prevents misuse. It is sufficiently complete for an agent to invoke the tool correctly without external knowledge.

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 all parameters. The description adds valuable parameter-usage guidance beyond the schema, such as 'combine keyword with region and category', 'set verified=true when the answer must rest on government documents', and concrete examples like query_policies(keyword='CBAM') and query_policies(keyword='ISCC', language='en'). This helps the agent choose effective 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 opens with an explicit verb and resource: 'search the global rCB regulation library'. It then enumerates the covered jurisdictions and frameworks (EU CBAM/EUDR/ESPR, China MIIT, India/Korea EPR, US), which clearly identifies the tool's scope and differentiates it from singular get_policy or other query_* tools.

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?

Guidelines are explicit and actionable: 'combine keyword with region and category' and 'set verified=true when the answer must rest on government documents'. Limits also state when the tool is not appropriate ('no legal advice and no ruling on how a rule applies to a specific company or shipment'). However, it does not explicitly name sibling alternatives or state when to choose get_policy instead.

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

All Trustbase Lab · rCB & Chemical Recycling Data toolsInspect
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