Trustbase Lab · Trusted Data Infrastructure for the AI Era

rCB vs Virgin Carbon Black Price Benchmark

get_price_benchmark

Read-onlyIdempotent

Purpose: return the rCB and virgin carbon black price benchmark structure - the virgin N550 series as anchor, the rCB band expressed as 25-40% of that anchor, feedstock prices, international references, regional spreads, grade-level bands and cost structure. Guidelines: leave product and section empty for the full set; narrow with section='rCB' / 'feedstock' / 'international' / 'cost'; pair with get_elt_price_index for feedstock indices and get_rcb_index for the layered index series. Limits: reference bands and relative structure only - no exchange quote and no trading recommendation; ELT feedstock absolute prices are deliberately not published; every figure is a range, never a single transactable value. Ex: get_price_benchmark(section='rCB'), get_price_benchmark(product='N330', language='en'), get_price_benchmark(section='cost', response_format='json').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product`	No	产品关键词，如 'rCB N550'、'废轮胎'、'裂解油'、'N330'；英文模式如 'rCB N550'、'N330'。留空返回全部章节
`section`	No	章节关键词，如 'rCB'、'原料'、'国际'、'成本'；英文模式如 'rCB'、'cost'、'regional'。留空返回全部章节
`language`	No	输出语言 / output language (en = full English price tables)	zh
`response_format`	No	输出格式 / output format (json = 结构化价格数据，含 anchor/basis/sections，便于 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

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description goes further, stating no exchange quotes, no trading recommendations, ELT feedstock prices deliberately unpublished, and every figure is a range. These are critical behavioral constraints that annotations cannot convey. No contradiction with annotations.

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?

Well-structured with Purpose, Guidelines, Limits, and Ex sections. Information is front-loaded, each sentence carries distinct value, and no filler exists. Length is justified by the complexity of the tool.

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?

Despite having an output schema (which covers return values), the description covers usage patterns, limitations, and examples. For a tool with optional parameters and multiple sections, this is complete and anticipates agent needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant usage context: how to combine section and product, examples for each parameter, and clarifies that response_format='json' yields structured data for parsing. It enriches the schema without redundancy.

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 returns the rCB and virgin carbon black price benchmark structure, enumerating its components (anchor, band, feedstock, international, regional, grade, cost). It distinguishes itself from siblings by naming get_elt_price_index and get_rcb_index as complementary tools, so an agent can tell it apart.

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?

Explicitly states when to leave parameters empty for full set, how to narrow via section, and explicitly pairs with two sibling tools. Includes concrete usage examples. This is exemplary routing 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 · 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?