Trustbase Lab · rCB & Chemical Recycling Data

Search Standards & Technologies

query_techs

Read-onlyIdempotent

Purpose: search the rCB technology and standards library - ASTM D36 committee series (D8178 / D8466 / D8474 /D8632 / D1618 / D1506 / D8491 / D8585), Chinese standards (HG/T 5459 / GB/T 40009 / GB/T 19208 / GB/T 13460 /GB/T 3782 / T/CTRA 01), continuous pyrolysis processes, rCB post-treatment and sustainable carbon black.Guidelines: combine keyword with category (terminology / test / product / process / traceability) and region;use verified=true to keep only entries backed by standard texts. Limits: standard summaries and key technicalparameters only - full standard text is never reproduced; C-grade entries are unverified leads; the categorytaxonomy is ours, not the issuing body's. Ex: query_techs(keyword='TGA'), query_techs(category='测试标准'),query_techs(keyword='ASTM', language='en').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	返回条数上限（默认 20，最大 100）
`region`	No	地区/组织过滤，如 '国际'、'中国'、'欧盟'、'ASTM'
`keyword`	No	关键词模糊匹配，如 'ASTM'、'TGA'、'GB/T'、'热裂解'、'分类'
`category`	No	类别过滤，如 '术语标准'、'测试标准'、'产品标准'、'工艺技术'、'追溯标准'
`language`	No	输出语言	zh
`verified`	No	true=只看 A 级已核实条目
`confidence`	No	置信度：A=官方标准原文核实, B=权威二手来源, C=待核实
`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"
+}

First observedSep 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses meaningful behavioral constraints: only summaries and key parameters are returned, full standard text is never reproduced, C-grade entries are unverified leads, and the category taxonomy is the tool's own rather than the issuing body's. This materially shapes agent expectations.

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 organized into Purpose/Guidelines/Limits/Ex with no filler. The scope enumeration is dense but informative, and the examples are pragmatic invocation hints that earn their place.

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?

With 8 optional parameters and an output schema present, the description covers scope, query strategy, reliability caveats, and example calls. Nothing an agent needs to invoke 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; the description adds value by recommending parameter combinations, mapping category labels in English to the Chinese enum values, and clarifying verified=true and C-grade semantics. This goes beyond bare schema repetition.

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 ('search') and resource ('rCB technology and standards library'), then names concrete scope: ASTM D36 series, Chinese standards, continuous pyrolysis, post-treatment, and sustainable carbon black. This clearly differentiates it from sibling get_tech, which implies a single-record lookup, and from other query_* tools.

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 explicit guidance: combine keyword with category and region, use verified=true for standards-backed entries, and includes three example invocation patterns. It does not explicitly name sibling alternatives or state when not to use this tool, so it stops short of a 5.

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?