Trustbase Lab · Trusted Data Infrastructure for the AI Era

Get Company Detail

get_company

Read-onlyIdempotent

Purpose: fetch one company or project record (rCB producer / international player / equipment vendor) by entity id or name, returning the full detail including capacity, process, certification, investment, recent developments and source. Guidelines: ids come from query_companies (rcb-cn-xxx / rcb-gl-xxx / rcb-eq-xxx); pass name 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; sourced fields (capacity, investment, contacts) may all fields are public - low-confidence records are returned with their C confidence label rather than withheld; a name lookup returns the first match only and is not a disambiguation service. Ex: get_company(id='rcb-cn-001'), get_company(name='Pyrum'), get_company(name='Plastic Energy', language='en').

Input 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

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

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, and the description adds real behavioral context beyond them: one record per call with no batch mode, low-confidence records returned with a C label rather than withheld, and name lookup returning only the first match (not a disambiguation service). These are operational traits an agent cannot infer from structured fields.

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?

Front-loaded Purpose/Guidelines/Limits/Ex structure with worked examples that earn their place. It loses a point for the garbled clause 'sourced fields (capacity, investment, contacts) may all fields are public', which breaks the sentence mid-thought and slightly muddies the Limits section.

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 an output schema present, return-value detail is unnecessary, and the description covers everything else an agent needs: lookup modes, parameter toggles, scope limits, confidence handling, and examples. Nothing needed to call 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 baseline is 3; the description adds value by giving id format examples (rcb-cn-xxx / rcb-gl-xxx / rcb-eq-xxx), clarifying name is a fuzzy Chinese-or-English keyword lookup, and explaining language='en' and response_format='json' intent. It stops short of documenting the anyOf id-or-name requirement explicitly, but the examples and guidelines effectively convey it.

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 (fetch) and resource (one company/project record), enumerates the entity types covered (rCB producer / international player / equipment vendor), and specifies what is returned (capacity, process, certification, investment, developments, source). An agent can tell it apart from query_companies, the search sibling, without opening a schema.

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?

Explicitly routes the agent: ids come from query_companies, use name for fuzzy lookup when the id is unknown, and it notes language/response_format toggles with concrete examples. The alternatives and the condition selecting each lookup mode are spelled out, not left to inference.

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?