Trustbase Lab · rCB & Chemical Recycling Data

ELT Recycling Data

get_elt_recycling

Read-onlyIdempotent

Purpose: the end-of-life tyre (ELT) collection topic for the rCB supply chain - policy targets, the 2026 standard system, the collection-network build-out, the processing value ladder (retreading > recycled rubber > pyrolysis) and market-size figures, with official sources labelled per record. Guidelines: call with no arguments for the full topic, or pass topic (policy/standard/network/ladder/market) to focus one section; pair with get_elt_price_index (category G-ELT) for collection prices and get_feedstock_overview for arisings. Limits: policy and standard records are sourced from official documents; market-size figures are public-information compilations and labelled as such; does not return prices. Ex: 'China end-of-life tyre recycling policy 2030 target', 'ELT collection network China', 'scrap tyre pyrolysis standards 2026'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No	可选：policy(政策目标) / standard(标准体系) / network(回收网络) / ladder(价值阶梯) / market(市场数据)
`language`	No	可选：返回语言

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"
+}

AddedSep 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful behavioral context: official sources are labelled per record, market-size figures are public-information compilations and labelled as such, and the tool deliberately excludes prices. This goes beyond the annotation safety profile and helps the agent set expectations about data provenance and coverage.

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 well-structured with labelled sections (Purpose, Guidelines, Limits, Ex). Each sentence contributes either scope, usage direction, limitations, or examples. Despite being longer than average, there is no redundancy, and the most important purpose and usage information is front-loaded.

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 tool with 2 optional parameters, an output schema, and clear annotations, the description fully covers what the tool returns, how to filter it, what it excludes, and how it relates to sibling tools. The examples illustrate realistic queries. Nothing an agent needs to select and invoke the tool 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 schema already documents both parameters. The description adds value by explaining that no arguments returns the full topic, that topic narrows to one section, and by giving concrete query examples for topic values. This clarifies parameter usage beyond the schema's terse value list.

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 a precise statement of the resource: the end-of-life tyre (ELT) collection topic for the rCB supply chain, enumerating specific content areas (policy targets, 2026 standard system, collection network, value ladder, market sizes). It also names the sibling tools it should be paired with and clarifies it does not return prices, effectively distinguishing it from get_elt_price_index and get_feedstock_overview.

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 Guidelines section is explicit: call with no arguments for the full topic, or pass a topic value to focus one section. It also names alternatives and complements: pair with get_elt_price_index for collection prices and get_feedstock_overview for arisings. Limits explicitly state what this tool does not do (returns prices), so an agent knows when not to use it.

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?