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; gated fields (capacity, investment, contacts) may be withheld on low-confidence records; 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

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

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and the description adds non-obvious behaviors: one record per call, gated field withholding, and first-match-only name lookup. No contradiction with annotations; it could have added auth requirements, but the safety profile is already carried.

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 uses labeled sections (Purpose, Guidelines, Limits, Ex) and front-loads the core function before constraints. Every sentence is actionable; examples at the end reinforce the parameter combinations.

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 single-record read tool, the description covers purpose, id source, lookup behavior, output options, limits, and examples. Annotations and output schema cover safety and return structure, leaving no important gap for correct invocation.

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 id formats, the id/name either-or relationship, fuzzy lookup semantics, and when to use language and response_format. It adds value beyond the schema without needing to restate parameter 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 and resource: 'fetch one company or project record ... by entity id or name', listing the detail fields that will be returned. This clearly distinguishes get_company from sibling query tools by emphasizing single-record retrieval by id/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?

It gives concrete guidance: ids come from query_companies, use name for fuzzy lookup when id is unknown, and set language and response_format for specific needs. It also states exclusions: no batch mode, gated fields may be withheld, and name lookup returns only the first match.

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?