Trustbase Lab · Trusted Data Infrastructure for the AI Era

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. Also returns a PUBLIC-SOURCE INDEX SERIES (monthly, base month = 1000) covering the tyre value chain: scrap tyre, 24-mesh crumb rubber, pyrolysis oil, and virgin carbon black grades N220/N330/N550/N660, with category-to-anchor ratios - use it for trend direction and cross-category structure (the virgin carbon-black grades act as the rCB benchmark). This series is index-only and unit-less: it cannot be reverse-engineered into absolute 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.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on substantive behavioral context beyond them: values are index-only and unit-less, cannot be reverse-engineered into absolute prices, absolute prices and source platforms are never disclosed, the series is monthly with base month = 1000, and regions are deliberately excluded from a category when caliber is not comparable (China bead wire vs EU/US mixed wire). No contradiction with the annotations.

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

Conciseness3/5

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

Front-loaded with labeled 'Purpose'/'Guidelines'/'Limits' sections and closing examples, which is good structure, but the prose is very long and partly redundant ('This series is index-only and unit-less' is restated as 'index values, region spreads and ratios only - absolute prices ... never disclosed'). Several sentences could be merged without losing information.

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?

With an output schema present, the description need not explain return values, and it instead covers the residual gaps an agent would care about: index-only semantics, unit-lessness, base month, the region-comparability exclusion rule, and cross-tool pairing. Nothing required to select or 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% and the schema already documents tier/region/category, so the baseline is 3; the description goes further by explaining the semantics of each mode (tier 1 vs tier 2, region codes EU/US/CN/CA/IN, category codes and their expansions) and how the parameters compose. It does not, however, state behavior for invalid or conflicting 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 names a specific resource (rCB feedstock / end-of-life tyre price index) and precisely scopes it: Tier 1 global categories (G-TPO/G-CRB/G-WIRE/G-RCB), Tier 2 region-specific categories, and an index-only public-source series with base month 1000. It explicitly distinguishes itself from get_feedstock_overview (arisings/processing paths) and get_rcb_index (layered rCB product prices), so an agent can route between them without opening a schema.

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' block gives an explicit condition-to-result mapping: no arguments = global cross-section with region spreads, pass region = that region's index across categories, pass category = one category's region comparison. It also names two complementary siblings to pair with. It stops short of stating when NOT to use this tool or which sibling supersedes it in ambiguous cases.

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?