Skip to main content
Glama

Trustbase Lab · rCB & Chemical Recycling Data

by com.trustbaselab
OverviewDiscussionsAdmin

Search Carbon Black Grades

query_grades
Read-onlyIdempotent

Purpose: search the carbon black grade benchmark library - ASTM D1765 native grades (N110-N990, SAF/ISAF/HAF/FEF/GPF/SRF/MT/FT), conductive specialty benchmarks (acetylene black, Super P, ENSACO 250G, Vulcan XC-72R, Ketjenblack EC-300J/EC-600JD) and rCB types - with 6 standard parameters each (iodine absorption, OAN, BET, ash, volatile, sieve residue). Guidelines: combine type='native'/'conductive'/'rcb', category (e.g. 'HAF','FEF'), keyword ('N550','N330','Super P'); use as the anchoring benchmark layer before any rCB vs native comparison; rCB records include vs-N550 gap analysis. Limits: 37 records (29 native + 6 conductive + 2 rCB types) - spec ranges, not lot CoA; ash gap (rCB 8-15% vs N550 <=0.5%) caps rCB at semi-reinforcing uses. Ex: 'N330 standard parameters', 'conductive carbon black for lithium battery', 'rCB vs N550'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo类型过滤：native=原生炭黑, rcb=再生炭黑, conductive=导电特种炭黑
limitNo返回条数上限（默认 50，最大 100）
keywordNo牌号/名称关键词，如 'N550'、'N330'、'HAF'、'FEF'、'Super P'、'rCB-General'
categoryNo段位过滤，如 'SAF'（超耐磨）、'ISAF'（中超耐磨）、'HAF'（高耐磨）、'FEF'（快压出）、'GPF'（通用）、'SRF'（半补强）、'MT'（中粒子热裂）、'FT'（大粒子热裂）、'导电'（conductive 类）
languageNo输出语言zh
confidenceNo置信度过滤
response_formatNo输出格式：markdown=人类阅读, json=Agent 处理友好markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesHuman-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"段位过滤，如 'SAF'（超耐磨）、'ISAF'（中超耐磨）、'HAF'（高耐磨）、'FEF'（快压出）、'GPF'（通用）、'SRF'（半补强）、'MT'（中粒子热裂）、'FT'（大粒子热裂）"New value: +"段位过滤，如 'SAF'（超耐磨）、'ISAF'（中超耐磨）、'HAF'（高耐磨）、'FEF'（快压出）、'GPF'（通用）、'SRF'（半补强）、'MT'（中粒子热裂）、'FT'（大粒子热裂）、'导电'（conductive 类）"
    • changedInput schema / properties / keyword / description
      Previous value: -"牌号/名称关键词，如 'N550'、'N330'、'HAF'、'FEF'、'rCB-General'"New value: +"牌号/名称关键词，如 'N550'、'N330'、'HAF'、'FEF'、'Super P'、'rCB-General'"
    • changedInput schema / properties / type / description
      Previous value: -"类型过滤：native=原生炭黑, rcb=再生炭黑"New value: +"类型过滤：native=原生炭黑, rcb=再生炭黑, conductive=导电特种炭黑"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "native",
-  "rcb"
-]New value: +[
+  "native",
+  "rcb",
+  "conductive"
+]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral boundaries: exactly 37 records, spec ranges rather than lot CoA, rCB vs-N550 gap analysis, and the ash-gap limitation on rCB reinforcement. This materially prevents agents from misinterpreting the data as lot-specific or broader than it is.

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 dense but organized into Purpose/Guidelines/Limits/Ex segments and front-loads the resource. A few semicolon-packed clauses reduce readability, but every sentence contributes domain-relevant constraints or usage guidance.

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?

For a 7-parameter, all-optional search tool with a complete schema, annotations, and an output schema, the description covers library composition, dataset limits, filter-combination guidance, and example queries. Nothing essential for selecting or invoking the tool appears to be 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 description coverage is 100%, with each parameter already explained. The description adds value by showing how to combine type, category, and keyword, and by giving example query intents. It doesn't deeply explain parameter formats, but that's unnecessary given the schema's completeness.

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 and resource: 'search the carbon black grade benchmark library' with explicit scopes (ASTM D1765 native grades, conductive benchmarks, rCB types). The word 'search' plus the enumerated contents distinguishes it clearly from sibling tools like get_grade or get_grade_spec.

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?

Provides an explicit Guidelines section telling agents to combine type/category/keyword and to use this tool 'as the anchoring benchmark layer before any rCB vs native comparison'. It also gives concrete example queries, but it does not name sibling tools to use instead under specific circumstances, so it lacks explicit when-not/alternative 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 toolsInspect
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