Trustbase Lab · rCB & Chemical Recycling Data

Search Companies & Capacity Projects

query_companies

Read-onlyIdempotent

Purpose: query the global rCB company and project database (129 records: domestic / international / equipment vendors) by segment, region, status and keyword - the discovery tool for capacity projects and players in the chemical recycling industry. Guidelines: combine segment (rcb/virgin/conductive) + status ('在建','规划','under construction') + location; for capacity-project lists filter status, then pair with get_company for full entity detail. Limits: company-level records only - capacity is a record attribute, not a separate projects table; confidence varies A/B/C. Ex: 'rCB projects under construction in China', 'conductive carbon black producers worldwide'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`group`	No	数据分组：all=全部（默认）, domestic=中国国内, international=国际, vendors=设备厂商
`limit`	No	返回条数上限（默认 20，最大 100）
`region`	No	区域过滤（与 group 等价，兼容 AI Agent 习惯）
`status`	No	状态关键词，如 '在运'、'新建'、'在建'、'规划'
`keyword`	No	企业名或产品线模糊匹配，如 '炭黑'、'pyrolysis'
`segment`	No	业务板块过滤（schema 1.6 基准层）：rcb=再生炭黑业务, virgin=原生炭黑基准厂商, conductive=导电特种炭黑
`language`	No	输出语言：zh=中文（默认）, en=英文	zh
`location`	No	地点/国家关键词，如 '山东'、'德国'
`verified`	No	是否 Verified Supplier：true=只看 A 级可信供应商（AI Agent 推荐用）
`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"
+}

Changed1 schema field changedSep 17, 2026

addedInput schema / properties / segment

Added value: +{
+  "description": "业务板块过滤（schema 1.6 基准层）：rcb=再生炭黑业务, virgin=原生炭黑基准厂商, conductive=导电特种炭黑",
+  "enum": [
+    "rcb",
+    "virgin",
+    "conductive"
+  ],
+  "type": "string"
+}

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 declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond those: it discloses the record-level granularity ('capacity is a record attribute, not a separate projects table') and the confidence grading (A/B/C). It also explains that results are filtered to company-level records, which affects how an agent interprets results. No contradictions with annotations.

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 efficiently structured with labeled sections (Purpose, Guidelines, Limits, Example). The purpose is front-loaded, and every sentence carries functional weight—no filler. It is longer than a one-liner but justified given the tool's complexity (11 parameters, multiple filter dimensions) and the guidance it provides.

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?

The tool has 11 parameters (all documented), an output schema, and no nested objects. The description covers the discovery intent, filter combinations, record granularity, confidence levels, and pairing with get_company. An agent has everything needed to call the tool correctly, including example queries. The output schema handles return format, so no further description is required.

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?

Although the input schema covers all 11 parameters with descriptions (100% coverage), the description adds meaning beyond the schema by explaining how to combine parameters: 'combine segment (rcb/virgin/conductive) + status (在建/规划/under construction) + location' and by providing concrete example queries ('rCB projects under construction in China', 'conductive carbon black producers worldwide'). This elevates the semantic value beyond the schema's per-parameter documentation.

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 clear statement of purpose: 'query the global rCB company and project database... the discovery tool for capacity projects and players in the chemical recycling industry.' It specifies the resource (company/project database) and the verb (query), and differentiates from sibling get_company by noting it pairs for full entity detail. The scope is precise and immediately actionable.

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 provides explicit usage guidance: 'combine segment (rcb/virgin/conductive) + status (在建/规划/under construction) + location' and 'for capacity-project lists filter status, then pair with get_company for full entity detail.' It also states a clear limitation ('company-level records only - capacity is a record attribute, not a separate projects table'), which serves as a when-not and points to the correct alternative.

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?