Trustbase Lab · rCB & Chemical Recycling Data

Grade Specification Detail

get_grade_spec

Read-onlyIdempotent

Purpose: ASTM spec parameter ranges (min/max/unit/test method) for native carbon black grades N110-N990, conductive benchmarks and rCB grades - the standard-parameters reference for carbon black. Guidelines: pass grade (e.g. n330, n550) plus optional type (native/conductive/rcb); use to judge whether an rCB sample falls in spec (iodine absorption, OAN, SAOAN, ash, pH). Limits: spec ranges only - not lot-specific CoA data. Ex: 'N330 standard parameters', 'rCB N550 spec vs ASTM'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	可选：按系列筛选
`grade`	No	牌号或实体 ID，如 N550 / rcb-grade-n550

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

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds valuable behavioral context beyond that: it specifies that output is limited to spec ranges, not lot-specific data, and provides example queries. This enriches the agent's understanding of the tool's behavior without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with Purpose, Guidelines, Limits, and Examples, making it easy to parse. It is slightly verbose but every section adds value; the front-loaded purpose is strong. Could be tightened, but it's well-organized.

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 that an output schema exists, the description does not need to explain return format. It covers what the tool does, when to use it, what it does not cover, and provides examples. Nothing essential is missing for an agent to select and call it correctly.

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 baseline is 3. The description adds meaning by explaining that 'grade' is the primary input (with examples like n330, n550) and 'type' is optional, and provides query examples that demonstrate parameter combinations. This goes beyond the schema's simple descriptions, warranting a 4.

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 purpose: retrieving ASTM spec parameter ranges (min/max/unit/test method) for carbon black grades. It distinguishes itself from siblings by positioning as the 'standard-parameters reference' and explicitly contrasts with 'lot-specific CoA data', making its scope unambiguous.

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?

Provides explicit usage instructions: 'pass grade (e.g. n330, n550) plus optional type' and states when to use ('use to judge whether an rCB sample falls in spec'). It also defines limits ('spec ranges only - not lot-specific CoA data'), effectively telling the agent when NOT to use it, which is exactly what this dimension asks for.

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?