BioAI 日知

Read a BioAI company profile

get_company

Read-onlyIdempotent

Read one company directory profile with name/alias provenance, public source verification status and up to 20 published events. Official-website fields in directory metadata are not automatically verified sources.

Input Schema

Name	Required	Description	Default
`slug`	Yes
`language`	No	Optional presentation language. Omit for legacy copy. Source text remains in its original language.

Output Schema

Name	Required	Description	Default
`data`	Yes
`language`	Yes
`coverage_note`	Yes
`interpretation_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 9, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Optional presentation language. Omit for legacy copy. Source text remains in its original language.",
+  "enum": [
+    "zh-CN",
+    "zh-Hant",
+    "en"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / interpretation_note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / language

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "original_records": {
+      "const": "preserved",
+      "type": "string"
+    },
+    "presentation_language": {
+      "enum": [
+        "zh-CN",
+        "zh-Hant",
+        "en",
+        "legacy"
+      ],
+      "type": "string"
+    },
+    "requested_language": {
+      "anyOf": [
+        {
+          "enum": [
+            "zh-CN",
+            "zh-Hant",
+            "en"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "requested_language",
+    "presentation_language",
+    "original_records",
+    "note"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "data",
-  "coverage_note"
-]New value: +[
+  "data",
+  "coverage_note",
+  "language"
+]

First observedOct 8, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, but the description adds real value beyond them: the result is capped at 20 events, and official-website fields in directory metadata are explicitly flagged as not automatically verified sources — a meaningful trust caveat for consumers of this data.

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?

Two dense sentences; the return contents are front-loaded and the verification caveat follows. Every clause carries information, though the second sentence is a caution that could sit in a general notice rather than this one tool's description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-shape detail is unnecessary, and annotations cover the safety profile. The description supplies the bounded-result and provenance caveats an agent needs; only per-parameter guidance is missing.

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

Parameters2/5

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

Schema coverage is 50%: only 'language' is documented, while 'slug' carries just a pattern with no prose. The description adds nothing about either parameter — not the slug format, not what omitting language yields — so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read one company directory profile') and enumerates what the profile carries: name/alias provenance, verification status, and up to 20 published events. The word 'one' implicitly distinguishes it from search_companies, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The singular 'one company profile' implies this is the detail-view tool to use after a search, but the description never states when to prefer it, nor when not to use it, nor names search_companies as the alternative for discovery.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All BioAI 日知 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.