Trustbase Lab · rCB & Chemical Recycling Data

Calculate rCB Cost Saving

calculate_saving

Read-onlyIdempotent

Purpose: substitution economics compute for carbon black - given a native price (vcb_price_input), an rCB price (rcb_price_input) and replacement ratio, returns per-ton saving and optional annualized value. Guidelines: supply your own quotes, or fetch market anchors via get_rcb_index first. Limits: pure arithmetic - no market data access, not a price recommendation. Ex: 'N330 12000 RMB/t vs rCB 8000 RMB/t, ratio 0.3, annual 5000t'.

Input Schema

TableJSON Schema

Name	Required	Description
`ratio`	Yes	替代比例，0~1
`annual_volume_t`	No	可选，年用量（吨），用于年化
`rcb_price_input`	Yes	rCB 价格（正数，调用方提供）
`vcb_price_input`	Yes	原生炭黑价格（正数，调用方提供）

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

Behavior4/5

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

Annotations already declare read-only and idempotent behavior, and the description adds useful context: it is pure arithmetic, performs no market data access, and is not a price recommendation. This is consistent with the annotations and clarifies side-effect expectations well.

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 Purpose, Guidelines, Limits, and an Example. Every section adds useful information and the essential behavior is front-loaded before the example.

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 arithmetic tool with a complete input schema, output schema, and clear annotations, the description covers purpose, inputs, workflow, limits, and gives a concrete example. An agent has enough context to invoke it correctly and confidently.

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%, so the baseline is 3, but the description adds meaning by identifying which price is the native price, which is the rCB price, and how the replacement ratio and annual volume fit into the calculation. The example with 'N330 12000 RMB/t vs rCB 8000 RMB/t, ratio 0.3, annual 5000t' clarifies units and usage beyond the schema.

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 a specific verb and resource: it computes per-ton saving and optional annualized value from native and rCB prices plus replacement ratio. It also distinguishes itself from data-fetching siblings by emphasizing 'pure arithmetic - no market data access'.

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 description gives concrete guidance: supply your own quotes, or fetch market anchors via get_rcb_index first. It also states what the tool is not for ('not a price recommendation'), though it could more explicitly name sibling comparison/boundary tools as 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?