Trustbase Lab · rCB & Chemical Recycling Data

Get Grade Detail

get_grade

Read-onlyIdempotent

Purpose: fetch one carbon black grade in full - the six ASTM parameters as min/max ranges with their test-methodstandards, application list, process route, brand owner for conductive grades, and for rCB types a gap analysisagainst the virgin N550 anchor on iodine / DBP / BET / ash / heating loss / sieve residue. Guidelines: use thesemantic id (rcb-grade-n550 / rcb-grade-xc72 / rcb-grade-rcb-general) or the grade name ('N550', 'Super P','rCB-General'); pair with query_grades to discover ids and get_grade_spec for specification detail. Limits: onegrade per call; ranges are compiled from public specifications and are not a supplier's guaranteed certificateof analysis; the gap analysis is relative to N550 only, not to every virgin grade. Ex:get_grade(id='rcb-grade-n550'), get_grade(name='Super P'), get_grade(name='rCB-General',response_format='json').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	语义化实体 ID，如 rcb-grade-n550 / rcb-grade-xc72 / rcb-grade-rcb-general
`name`	No	牌号名（与 id 二选一），如 'N550'、'N660'、'N330'、'Super P'、'rCB-General'
`language`	No	输出语言	zh
`response_format`	No	输出格式：markdown=人类阅读, json=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"
+}

Changed2 schema fields changedSep 17, 2026

changedInput schema / properties / id / description

Previous value: -"语义化实体 ID，如 rcb-grade-n550 / rcb-grade-rcb-general / rcb-grade-rcb-refined"New value: +"语义化实体 ID，如 rcb-grade-n550 / rcb-grade-xc72 / rcb-grade-rcb-general"

changedInput schema / properties / name / description

Previous value: -"牌号名（与 id 二选一），如 'N550'、'N660'、'N330'、'rCB-General'"New value: +"牌号名（与 id 二选一），如 'N550'、'N660'、'N330'、'Super P'、'rCB-General'"

AddedSep 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the tool as readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds meaningful behavioral caveats beyond the annotations: the ranges are compiled from public specifications and are not a supplier certificate, and the gap analysis is relative only to N550. These constraints materially affect how an agent should interpret 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 Purpose, Guidelines, Limits, and Ex sections, front-loading the core purpose before usage details. Every sentence carries information; there is no filler or repetition of the schema's enum descriptions. Length is justified by the richness of the tool's output.

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?

Given the parameter count, 100% schema coverage, existing output schema, and strong sibling context, the description is complete. It covers invocation alternatives, data provenance, range semantics, a key comparator limitation, and realistic examples. Nothing an agent needs to correctly select and call this tool is missing.

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. The description adds value by clarifying the id/name alternatives and giving concrete examples such as get_grade(id='rcb-grade-n550') and get_grade(name='Super P', response_format='json'), which demonstrate the relationship between parameters. It does not add much beyond the schema for language and response_format, but the examples are genuinely useful.

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 opens with a specific verb and resource: 'fetch one carbon black grade in full', then enumerates exactly what is included: six ASTM parameters as min/max ranges, test-method standards, application list, process route, brand owner, and the N550-anchored gap analysis for rCB types. This level of detail clearly differentiates it from siblings like get_grade_spec and query_grades.

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?

Guidelines explicitly state how to call the tool by semantic id or grade name, and direct the agent to query_grades for id discovery and get_grade_spec for specification detail. Limits are also stated: one grade per call, ranges are from public specs not a guaranteed certificate, and gap analysis is only against N550. This is exemplary usage routing.

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?