Trustbase Lab · Trusted Data Infrastructure for the AI Era

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, dbp_absorption, bet_surface_area, ash_content, ph_value). Limits: spec ranges only - not lot-specific CoA data. Ex: 'N330 standard parameters', 'rCB N550 spec vs ASTM'. ⭐ Scope: SPEC-ONLY quick lookup (ASTM min/max/unit/test method). For application, process route, brand owner or rCB-vs-N550 gap analysis, use get_grade instead.

Input Schema

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

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

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real behavioral context beyond annotations: it explicitly limits output to spec ranges and excludes lot-specific CoA data, which sets expectations about result scope. Output format is deferred to the output schema, which is appropriate.

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?

Front-loaded with Purpose, then Guidelines, Limits, Examples, and Scope, so key routing info comes first. It is dense but each labeled section earns its place; the ⭐ marker is minor decoration that borders on unnecessary but doesn't harm retrieval.

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?

An output schema exists, so return-value detail needn't be in the description, and the description supplies purpose, filtering, limits, examples, and sibling differentiation. Nothing needed to call it correctly 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, but the description adds value by giving concrete grade examples (n330, n550), explaining the type filter (native/conductive/rcb), and enumerating which spec fields are judged (iodine_absorption, dbp_absorption, etc.). This meaningfully augments the terse schema 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?

States a specific verb (get) and resource (ASTM spec parameter ranges for carbon black grades) with explicit scope (N110-N990, conductive, rCB). It distinguishes itself from the sibling get_grade by labeling itself the SPEC-ONLY quick lookup, so an agent can route correctly without opening either schema.

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?

Gives explicit when-to-use guidance (judge whether an rCB sample falls in spec by listing the relevant properties), concrete example queries, and a clear exclusion routing to get_grade for application/process/gap analysis. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Trustbase Lab · Trusted Data Infrastructure for the AI Era 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?