Skip to main content
Glama

Trustbase Lab · Trusted Data Infrastructure for the AI Era

select_rcb_grade

select_rcb_grade
Read-onlyIdempotent

Purpose: rCB grade selector - take measured carbon-black parameters (iodine adsorption, DBP, BET, ash) or a target native grade, and return the closest grade, the rCB tier, the recommended substitution ratio for the application segment, and the MUST-TEST list. Guidelines: use for "can this rCB replace N550 / what grade is this / how much can I substitute" questions; supply ash whenever possible because ash is the single most discriminating parameter between rCB and virgin carbon black. Limits: parameters are RANGES not exact values, substitution ratios come from public sources and business judgment and are NOT guarantees, and the tool never returns formulations, process parameters or customer data. Ex: select_rcb_grade(iodine=40, dbp=118, ash=6), select_rcb_grade(target_grade='N550', application='foam').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "select_rcb_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
ashNo灰分(%),ASTM D1506(强烈建议提供,用于判 rCB 档位)
betNoBET 比表面积(m²/g),ASTM D6556(可选)
dbpNoDBP 吸油值(cm³/100g),ASTM D2414
iodineNo吸碘值 ADS(g/kg),ASTM D1510
languageNo输出语言zh
applicationNo用途段;决定建议替代比例
target_gradeNo对标原生牌号,如 N110/N220/N330/N550/N660/N774/N990
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (machine-readable).markdown

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses real behavioral limits: inputs are ranges, ratios derive from public sources plus judgment and are not guarantees, and no formulations, process parameters, or customer data are returned. That is meaningful context the annotations cannot carry.

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?

Labeled sections (Purpose / Guidelines / Limits / Ex) make it scannable and front-loaded, with no filler sentences. It is somewhat dense and the examples repeat ground already covered, but every section contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, read-only, zero-required tool with an output schema and full annotation coverage, the description supplies scope, limits, and usage examples. It does not explain how conflicting parameter sets or missing parameters are resolved, which is the only remaining ambiguity.

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 already 100%, yet the description adds semantics the schema lacks: ash is the single most discriminating parameter and should be supplied, application drives the substitution ratio, and two example invocations demonstrate realistic parameter combinations. Not a full 5 since much of the field meaning is already in the enum and property 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?

The description opens with a specific verb+resource ("rCB grade selector") and spells out exactly what comes back: closest grade, rCB tier, substitution ratio, MUST-TEST list. This clearly separates it from lookup siblings such as get_grade or get_grade_spec, which return stored grades rather than matching measured parameters.

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?

Concrete trigger questions are quoted ("can this rCB replace N550", "what grade is this", "how much can I substitute"), and two worked call examples show the two usage modes (parameter-based and target-grade-based). It stops short of naming when to use a sibling instead, so it is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources