Trustbase Lab · Trusted Data Infrastructure for the AI Era

Get Standard Detail

get_tech

Read-onlyIdempotent

Purpose: fetch one rCB technical standard or process by entity ID or keyword - ASTM D36 series (D8178/D8466/D8474...), Chinese GB/T, HG/T, continuous pyrolysis, sCB - with scope, core indicators, status and source link. Guidelines: pass id (e.g. rcb-tech-001) or name keyword ('D8178','pyrolysis','GB/T 40009'); use when an Agent needs the governing standard behind a parameter or certification claim. Limits: metadata + source link only - not full standard text (copyright); verify currency on the official standards platform before compliance use. Ex: 'ASTM D8178 scope', 'rCB national standard GB'.

Input Schema

Name	Required	Description	Default
`id`	No	实体 ID，如 rcb-tech-001
`name`	No	名称或标准号关键词（与 id 二选一），如 'D8178'、'GB/T 40009'
`language`	No	输出语言	zh
`response_format`	No	输出格式：markdown=人类阅读, json=Agent 处理友好	markdown

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 changedOct 12, 2026

addedInput schema / anyOf

Added value: +[
+  {
+    "required": [
+      "id"
+    ]
+  },
+  {
+    "required": [
+      "name"
+    ]
+  }
+]

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/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the safety profile is known. The description adds genuinely new behavioral context beyond that: output is metadata + source link only (not full copyright text) and currency must be verified on the official platform before compliance use. This is useful scope/limitation disclosure.

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?

Dense but labeled with Purpose/Guidelines/Limits/Ex so it is front-loaded and scannable. The acronym list and examples slightly pad length, but essentially every clause carries information; minor trimming only.

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?

With an output schema present, return-value explanation is not required, and the description appropriately focuses on scope, lookup keys, and limitations. Combined with annotations and full schema coverage, an agent has what it needs to call this correctly; only explicit sibling routing is absent.

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% with enum defaults documented, so the baseline is 3. The description adds practical value by giving concrete ID format ('rcb-tech-001') and keyword examples ('D8178', 'GB/T 40009') that illustrate the id/name trade-off the anyOf expresses only structurally.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('fetch one ... technical standard or process'), the resource domain (ASTM D36 series, GB/T, HG/T, pyrolysis, sCB), and the two lookup keys (entity ID or keyword). The word 'one' implicitly contrasts with the sibling query_techs list tool, but no sibling is named explicitly, so it falls short of a 5.

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?

Gives a concrete trigger: 'use when an Agent needs the governing standard behind a parameter or certification claim', plus worked examples ('ASTM D8178 scope'). It does not explicitly name alternative tools (get_carbon_standards, query_techs, get_grade_spec) or when-not-to-use, 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 · 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?