Trustbase Lab · Trusted Data Infrastructure for the AI Era

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-method standards, application list, process route, brand owner for conductive grades, and for rCB types a gap analysis against the virgin N550 anchor on iodine / DBP / BET / ash / heating loss / sieve residue. Guidelines: use the semantic 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: one grade per call; ranges are compiled from public specifications and are not a supplier's guaranteed certificate of 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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: ranges are compiled from public specifications and not a guaranteed certificate of analysis, and the gap analysis is relative to N550 only. These are non-obvious limits that prevent misinterpretation 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-organized with clear labels (Purpose, Guidelines, Limits, Ex) and immediately front-loads the purpose. Every sentence earns its place—no filler—and the examples are concise and instructive.

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 tool's moderate complexity (multiple return fields, gap analysis), the description covers what is fetched, how to identify the grade, edge cases (N550-only comparison), and usage limits. An output schema exists, so return-value details need not be repeated. The definition is complete enough for correct invocation.

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 meaning by showing concrete example values for id and name ('rcb-grade-n550', 'Super P') and clarifying the mutual-exclusivity via usage examples. However, it doesn't substantially expand beyond what the schema already documents for language or response_format.

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 states a specific verb and resource ('fetch one carbon black grade in full') and enumerates exactly what is returned: six ASTM parameters as min/max ranges, test-method standards, application list, process route, brand owner, and gap analysis for rCB types. This level of detail clearly distinguishes 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?

The description explicitly pairs this tool with query_grades to discover ids and with get_grade_spec for specification detail, signaling when to use each alternative. It also provides a Limits section clarifying one grade per call and the data provenance caveat, so an agent can decide confidently.

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?