BioAI 日知

Read a BioAI resource

get_resource

Read-onlyIdempotent

Read one stored source record by UUID, or an editor-reviewed event when kind='event'. Returns up to 6000 characters of stored source text, original URLs, publication status and provenance. It never retrieves arbitrary external URLs.

Input Schema

Name	Required	Description	Default
`id`	Yes
`kind`	No		record
`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.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld=false, so the bar is lower. The description adds genuinely new behavior: a 6000-character return cap, the exact payload contents (source text, URLs, status, provenance), and the important scope constraint that it never fetches arbitrary external URLs, which reinforces the openWorldHint=false annotation.

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?

Three tight sentences: identity/mode first, return payload second, the critical negative constraint last. No filler and every clause carries information.

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?

An output schema exists so return values need not be detailed, yet the description still summarizes them usefully. Combined with annotations covering the safety profile, an agent has everything needed to invoke this correctly.

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

Parameters3/5

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

Schema coverage is only 33%, so the description must compensate. It explains the record-vs-event semantics of kind and the UUID identity of id, but the language parameter and its 'omit for legacy copy' behavior are documented only in the schema, leaving a 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?

The description names a specific verb+resource ('Read one stored source record by UUID') and clarifies the dual mode via kind='event'. It implicitly distinguishes itself from list-style siblings like search_resources by emphasizing 'one', but never names an alternative tool.

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?

Usage is implied by the kind='event' branch and the UUID requirement, but the description never states when to prefer this tool over search_resources or get_source_status, nor any prerequisite for having a valid id. Adequate but with clear routing gaps.

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.