Trustbase Lab · rCB & Chemical Recycling Data

Price Trend Series

get_price_trend

Read-onlyIdempotent

Purpose: native carbon black / rCB price trend direction with official anchors only (no raw quote tables). Guidelines: pass optional segment (domestic/export/import/feedstock/rCB) and period (e.g. 2026); use for directional questions like 'is rCB price rising'. Limits: trend direction and anchors only - no absolute quotes; pair with get_rcb_index for numbers. Ex: 'rCB price trend 2026 CN'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No	可选：期别筛选，如 2026
`segment`	No	可选：国内 / 出口 / 进口 / 原料 / rCB

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

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description adds context beyond those: it discloses return constraints such as 'official anchors only', 'no raw quote tables', and 'trend direction and anchors only'. This clarifies what the agent will receive and what it will not, which is valuable for setting expectations.

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-organized with Purpose, Guidelines, Limits, and Ex labels, making it easy to scan. Every sentence contributes meaningful information without redundancy, and the most important purpose constraint is front-loaded. It is dense yet efficient.

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 simple two-optional-parameter read-only tool with an output schema and strong annotations, the description covers purpose, parameters, usage context, limitations, and a sibling alternative. No critical information appears missing for an agent to correctly select and invoke the tool.

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?

The schema already covers both parameters at 100%, but the description adds practical value by enumerating segment values in English (domestic/export/import/feedstock/rCB), giving a concrete period example (2026), and emphasizing both are optional. The example 'rCB price trend 2026 CN' makes parameter usage more concrete than the schema alone.

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 function: returning native carbon black / rCB price trend direction with official anchors, not raw quote tables. It also distinguishes itself from get_rcb_index by noting that tool provides numbers while this one provides direction. This gives an agent a precise picture of what the tool does and what it does not do.

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?

Usage is explicitly guided: pass optional segment and period, use for directional questions like 'is rCB price rising', and pair with get_rcb_index for numeric values. It also states limits ('no absolute quotes'), making it clear when not to rely on this tool. The example query further anchors correct invocation.

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?