Trustbase Lab · rCB & Chemical Recycling Data

Compare rCB vs Virgin Carbon Black

compare_rcb

Read-onlyIdempotent

Purpose: quality benchmark - compare measured rCB sample parameters against a target native carbon black grade (e.g. N550) spec ranges; classify each parameter pass / light deviation / significant deviation. Guidelines: pass target_grade plus rcb_params (iodine_absorption, OAN, ash...); ideal for grading incoming rCB lots against a native anchor before substitution decisions. Limits: needs measured values as input - no lab data on file; thresholds follow the site's anchored-benchmark methodology, not customer specs. Ex: 'compare rCB sample vs N550'.

Input Schema

TableJSON Schema

Name	Required	Description
`rcb_params`	Yes	rCB 实测参数，如 {"iodine_absorption": 45}
`target_grade`	Yes	目标牌号，如 N550
`threshold_pct`	No	显著偏离阈值（默认 20，%）

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

Behavior5/5

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

The description discloses behavioral details beyond the annotations, including the classification into pass / light deviation / significant deviation and the dependency on measured values. It also clarifies that thresholds follow the site's own anchored-benchmark methodology, not customer specifications, which is important for correct interpretation of results.

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 labeled Purpose, Guidelines, Limits, and Example segments, making it highly scannable and front-loaded. Each sentence contributes meaningful operational guidance, and the example clarifies usage without unnecessary verbosity.

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?

The description fully covers the tool's purpose, input requirements, methodology, limitations, and a usage example. Combined with complete schema descriptions and an output schema, there is sufficient information for an agent to select and correctly 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?

Schema description coverage is 100%, so the baseline is 3, but the description adds semantic value by giving concrete examples for rcb_params such as iodine_absorption, OAN, and ash. It also grounds target_grade with the N550 example, providing context beyond the schema's short parameter descriptions.

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 explicitly states the tool's purpose: compare measured rCB sample parameters against a target native carbon black grade spec range and classify each parameter as pass, light deviation, or significant deviation. It is clearly differentiated from sibling get_* tools that only retrieve grade or spec data without performing a benchmark comparison.

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 provides clear usage context: ideal for grading incoming rCB lots against a native anchor before substitution decisions, and it specifies required inputs including target_grade and rcb_params. It also gives limits such as needing measured values and following the site's anchored-benchmark methodology rather than customer specs, but it does not explicitly name alternative sibling tools for cases where different input or methodology is needed.

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?