Trustbase Lab · rCB & Chemical Recycling Data

Get Article Detail

get_article

Read-onlyIdempotent

Purpose: fetch one article record in full - title, publish date, author, account, topic category, source URL,confidence and an AI-readable summary. Guidelines: accepts the id from query_articles (rcb-art-xxx) or a titlekeyword; run query_articles first when the id is unknown; pair with get_announcements_timeline for achronological view. Limits: metadata and summary only - the full article body is not served; one record percall. Ex: get_article(id='rcb-art-001'), get_article(name='曼谷大会').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	实体 ID，如 rcb-art-001
`name`	No	标题关键词（与 id 二选一），如 '曼谷大会'、'EPDM'
`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"
+}

AddedSep 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds valuable behavioral constraints beyond annotations: it returns metadata and summary only, never the full body, and handles exactly one record per call. This is useful context that the annotations do not convey.

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 labeled structure (Purpose, Guidelines, Limits, Ex) is clear, front-loaded, and free of fluff. Minor typographical issues like 'titlekeyword', 'achronological', and 'URL,confidence' slightly reduce polish but do not harm comprehension.

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 read-only, single-record lookup with a rich schema and output schema, this description is complete: it covers what the tool returns, how to find the id, the one-of parameter behavior, the body limitation, and a pairing suggestion. There is no additional information an agent needs to call it correctly.

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, but the description adds meaning: it explains that id comes from query_articles with the rcb-art-xxx format, shows concrete examples for both id and name, and clarifies the one-record limit. Language and response_format are already well documented in the schema.

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 names a specific verb and resource (fetch one article record) and enumerates the exact fields returned, making its purpose unmistakable. It also differentiates from sibling tools by noting it takes an id from query_articles and returns one record, so an agent can distinguish it from other get_* and 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing guidance: run query_articles first when the id is unknown, use a title keyword as an alternative, and pair with get_announcements_timeline for chronological views. It also states an exclusion—full article body is not served—so an agent knows not to use this tool for that purpose.

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?