Trustbase Lab · rCB & Chemical Recycling Data

Get Policy Detail

get_policy

Read-onlyIdempotent

Purpose: fetch one regulation record in full - issuing body, policy type, scope, impact on the rCB industry,compliance deadline, source link and an AI-readable summary. Guidelines: accepts the id from query_policies(rcb-pol-xxx) or a name/identifier keyword such as 'CBAM' or '2023/956'; run query_policies first when the id isunknown; add response_format='json' for agent pipelines. Limits: one record per call; no legal opinion and noapplicability assessment for a given company, product or shipment. Ex: get_policy(id='rcb-pol-001'),get_policy(name='CBAM'), get_policy(name='2023/956', language='en').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	实体 ID，如 rcb-pol-001
`name`	No	名称关键词或文号（与 id 二选一），如 'CBAM'、'2023/956'
`language`	No	输出语言	zh
`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.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description adds important behavioral limits: 'one record per call' and 'no legal opinion and no applicability assessment for a given company, product or shipment.' This prevents an agent from overreaching the tool's scope, which is valuable context the annotations alone don't provide.

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

Conciseness5/5

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

The description is organized into Purpose, Guidelines, Limits, and Ex sections, each earning its place. It is dense but not bloated, with examples at the end to reinforce correct invocation without unnecessary prose.

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?

For a single-record read tool with an output schema, the description is complete: it explains what the tool returns, how to get the id, what it cannot do, and provides invocation examples. The annotations cover safety, and the output schema covers return structure, so nothing an agent needs to call it correctly is missing.

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 100%, so the baseline is 3, but the description enriches the parameter semantics with concrete examples ('cbam', '2023/956'), the relationship between id and name, and the source of valid IDs (query_policies). It also adds practical guidance on response_format for agent pipelines, going beyond the schema's default-only descriptions.

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: 'fetch one regulation record in full' and enumerates the exact fields returned (issuing body, policy type, scope, impact, compliance deadline, source link, summary). It clearly distinguishes itself from the sibling query_policies by focusing on retrieving a single record detail rather than listing/searching policies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use the tool: accept an id from query_policies or a name/identifier keyword, and instructs agents to run query_policies first when the id is unknown. It also provides concrete usage guidance for response_format='json' in agent pipelines, making the alternative workflow clear.

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 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?