Trustbase Lab · rCB & Chemical Recycling Data

rCB Price Index

get_rcb_index

Read-onlyIdempotent

Purpose: rCB price index query - returns the index (ABP), absolute reference price (ARP, USD/ton FOB) and AF/VF attribution decomposition for a grade level, period and region; native-carbon-black-anchored (N550 anchor method). Guidelines: pass grade (P1 refined / P2 standard / P3 industrial, default P2), date (YYYY-MM, blank = latest) and region (CN/EU/NA/SEA, default CN); pair with get_rcb_vcb_spread for discount and get_grade_trend for history. Limits: reference range computed from the anchor method - not a transaction price; VF factor is forward-only (no backfill before 2026-Q3). Ex: 'rCB index P2 CN 2026-09', 'current rCB reference price EU'.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	期别 YYYY-MM；留空取最新可用期
`grade`	No	发布层级，默认 P2
`region`	No	区域，默认 CN

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 17, 2026

TDQS

A4.6/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, so the safety profile is known. The description adds valuable behavioral context beyond this: it states the reference range is computed via the anchor method and is not a transaction price, and that the VF factor is forward-only (no backfill before 2026-Q3). This gives the agent important caveats about the data's nature and temporal limitations, which is beyond what annotations 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 well-structured with clear sections (Purpose, Guidelines, Limits, Example). It is front-loaded with the core purpose, then provides actionable guidance, limitations, and a concrete example. Every sentence earns its place—there is no fluff or repetition. The example usage ('rCB index P2 CN 2026-09', 'current rCB reference price EU') is practical and demonstrates natural language invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is highly complete given the tool's complexity. It covers the anchor method, parameter semantics, defaults, limitations, and even provides examples. Since an output schema exists, the description does not need to detail return values. It explains key caveats (non-transaction price, forward-only VF) that affect interpretation. The only minor gap is lack of explicit handling for invalid inputs or edge cases, but this is acceptable given the output schema and the thorough parameter guidance.

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 each parameter has a description in the schema. However, the tool description adds meaning beyond the schema: it explains the grade levels (P1 refined / P2 standard / P3 industrial) which are not defined in the enum descriptions, and clarifies the date format and default behavior (blank = latest) and region defaults. This enriches the agent's understanding of parameter choices.

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 clearly states the tool's purpose: a query that returns the rCB price index (ABP), absolute reference price (ARP), and AF/VF decomposition for a given grade, period, and region. It specifies the anchor method (N550) and distinguishes itself from other price tools by naming exactly what it returns. The verb 'query' and resource 'rCB price index' are precise, and the mention of the anchor method helps differentiate it from other index tools like get_elt_price_index.

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 provides explicit guidelines: how to pass each parameter (grade with defaults, date format and blank behavior, region with defaults), and it explicitly recommends pairing with get_rcb_vcb_spread for discount and get_grade_trend for history. It also discloses limitations (reference range is not a transaction price; VF is forward-only). This is comprehensive, telling the agent exactly when and how to use this tool and when to use alternatives.

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?