BioAI 日知

Search BioAI resources

search_resources

Read-onlyIdempotent

Search stored public research abstracts and industry source records by keywords, topic, academic/industry category and time window. days=0 searches all stored dates. This tool searches source records; it does not claim they are editor-reviewed news.

Input Schema

Name	Required	Description	Default
`days`	No
`limit`	No
`query`	No
`topic`	No
`offset`	No
`company`	No
`academic`	No		all
`language`	No	Optional presentation language. Omit for legacy copy. Source text remains in its original language.
`journal_tier`	No		selected

Output Schema

Name	Required	Description	Default
`items`	Yes
`limit`	Yes
`total`	Yes
`offset`	Yes
`language`	Yes
`coverage_note`	Yes
`interpretation_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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 / items / items / properties / display_labels

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

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: -[
-  "total",
-  "items",
-  "limit",
-  "offset",
-  "coverage_note"
-]New value: +[
+  "total",
+  "items",
+  "limit",
+  "offset",
+  "coverage_note",
+  "language"
+]

First observedOct 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds genuine value by disclosing a scope/trust caveat (sources are not asserted to be editor-reviewed) and the days=0 special case, but says nothing about pagination, result caps, or rate limits.

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?

Three tight sentences with the core purpose front-loaded and the caveat placed last. Every sentence carries weight, though the editorial caveat could be trimmed slightly.

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

Completeness3/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 described. However, for a 9-parameter tool with only 11% schema coverage, the description leaves too many parameters and no pagination/filtering guidance for a fully complete picture.

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 description coverage is only 11%, so the description must compensate. It maps keywords to query, topic to the topic enum, academic/industry category to academic, and time window to days (with the days=0 edge case), but leaves limit, offset, company, language, and journal_tier entirely unaddressed.

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 states a specific verb ('search') and resource ('stored public research abstracts and industry source records'), and clarifies the tool does not claim sources are editor-reviewed. It is clearly distinguishable from get_resource and search_companies by resource type, though it doesn't name those siblings 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?

Usage is implied by the search-verb framing, but there is no explicit when-to-use guidance or routing against alternatives like get_resource or get_source_status. The one hint, 'days=0 searches all stored dates,' is a parameter detail rather than selection guidance.

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.