Trustbase Lab · rCB & Chemical Recycling Data

End-of-Life Tire Price Index

get_elt_price_index

Read-onlyIdempotent

Purpose: rCB feedstock (end-of-life tyre) price index in GLOBAL caliber - Tier 1 global categories (scrap tyre collection price / tyre pyrolysis oil / crumb rubber / recovered steel wire / rCB) with region-by-region indices benchmarked to the global weighted average = 1000, plus Tier 2 region-specific categories (EU/US gate fee and TDF; CN rubber fuzz, rubber block, 900-mesh and 24-mesh powder). The first category is the scrap tyre collection price (G-ELT) - the single largest cost item for rCB producers. Guidelines: no arguments returns the global cross-section with region spreads; pass region (EU/US/CN/CA/IN) for that region's index across categories; pass category (G-TPO/G-CRB/G-WIRE/G-RCB) for one category's region comparison. Pair with get_feedstock_overview for arisings and processing paths, and get_rcb_index for layered rCB product prices. Limits: index values, region spreads and ratios only - absolute prices and source platforms are never disclosed because no official public statistics source exists for ELT feedstock prices worldwide; some regions are excluded from a category when the product caliber is not comparable (e.g. China's bead wire is a finished product vs the recovered mixed wire traded in the EU/US). Ex: 'global tyre pyrolysis oil price index vs China', 'crumb rubber price by region', 'which region has the highest TPO price'.

Input Schema

TableJSON Schema

Name	Required	Description
`tier`	No	可选：1=全球通用品类，2=区域特定品类
`region`	No	可选：区域代码 EU / US / CN / CA / IN —— 返回该区域在各全球品类上的指数
`category`	No	可选：全球品类代码 G-TPO(裂解油) / G-CRB(胶粉) / G-WIRE(钢丝) / G-RCB(再生炭黑)；或区域品类 R-GATEFEE 等

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.6/5.0

Behavior5/5

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

Beyond read-only/idempotent annotations, the description discloses important behavioral limits: only index values and ratios are returned, absolute prices and source platforms are never disclosed, and some regions are excluded when product caliber is incomparable. It also reveals the 1000-point benchmark basis, which is meaningful context an agent would not otherwise know.

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?

Longer than necessary for a simple tool, but it is clearly organized under Purpose, Guidelines, Limits, and Ex labels and front-loaded with the core purpose. The additional details about category context and data limitations justify most of the length.

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?

The definition covers default behavior, parameter combinations, category codes, regional limitations, output restrictions, and related tools, while an output schema exists for return value structure. For a multi-tier, multi-region index tool, this is sufficient for correct invocation.

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 for parameters is 100%, but the description adds value by explaining the practical effect of omitting arguments, listing region codes, supplying category codes (G-TPO/G-CRB/G-WIRE/G-RCB), and giving query examples. The tier parameter is only indirectly explained through the Tier 1/Tier 2 category descriptions, but the schema handles its basic definition.

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 identifies a specific resource ('rCB feedstock (end-of-life tyre) price index'), defines its global caliber, lists Tier 1 and Tier 2 categories, and clarifies the benchmark (global weighted average = 1000). It also states the primary use case for the scrap tyre collection price, making the tool's scope unmistakable against siblings like get_rcb_index.

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 Guidelines section explicitly covers no-argument, region, and category invocation modes, and names two sibling tools for complementary use. It stops short of explicitly saying when not to use this tool versus alternatives, but the invocation conditions and examples provide clear selection guidance.

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?