Trustbase Lab · rCB & Chemical Recycling Data

Get Company Detail

get_company

Read-onlyIdempotent

Purpose: fetch one company or project record (rCB producer / international player / equipment vendor) by entityid or name, returning the full detail including capacity, process, certification, investment, recentdevelopments and source. Guidelines: ids come from query_companies (rcb-cn-xxx / rcb-gl-xxx / rcb-eq-xxx); passname for fuzzy lookup when the id is unknown; add language='en' for English output and response_format='json'for agent parsing. Limits: one record per call, no batch mode; gated fields (capacity, investment, contacts) maybe withheld on low-confidence records; a name lookup returns the first match only and is not a disambiguationservice. Ex: get_company(id='rcb-cn-001'), get_company(name='Pyrum'), get_company(name='Plastic Energy',language='en').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	实体 ID，如 rcb-cn-001 / rcb-gl-005 / rcb-eq-003
`name`	No	企业名称关键词（与 id 二选一，支持中文或英文名）
`language`	No	输出语言：zh=中文（默认）, en=英文	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"
+}

First observedSep 15, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive, and the description adds meaningful behavioral context beyond them: no batch mode, gated fields may be withheld for low-confidence records, and name lookup is a first-match service rather than a disambiguation service. This accurately discloses important limitations.

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, and Examples, with every sentence carrying operational value. Minor typos do not undermine its clarity, and the practical examples make it immediately actionable for an agent.

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?

Given the output schema exists, the description does not need to explain return values. It covers purpose, parameter selection, source of valid ids, output-language/format switches, record-count limits, gated-field caveats, and disambiguation limitations – everything an agent needs to call this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial value by explaining the id/name relationship, that ids come from query_companies, that name is a fuzzy lookup, and by providing concrete examples. It also clarifies the purpose of language='en' and response_format='json' for agent consumption, going beyond the schema's enum 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 ('fetch') and a precise resource ('one company or project record'), scoping the tool to rCB producers, international players, or equipment vendors and listing the detail fields returned. It is clearly differentiated from siblings like query_companies by emphasizing single-record retrieval by entityid or name.

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 Guidelines section explicitly tells the agent where ids come from (query_companies), when to use fuzzy name lookup, and how to set language and response_format for agent parsing. It also states limits: one record per call, no batch mode, and name lookup returns only the first match and is not disambiguation – effectively defining when not to rely on this tool.

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?