kegg-mcp-server

get_ko_info

Read-onlyIdempotent

Retrieves KEGG Orthology (KO) entry details by KO ID, returning a compact summary or full flat-file parse for enzyme and pathway annotation.

Instructions

Get detailed information for a KEGG Orthology (KO) entry.

Args: ko_id: KEGG KO identifier (e.g. 'K00844' for hexokinase). detail_level: 'summary' (default, compact) or 'full' (complete flat-file parse).

Input Schema

Name	Required	Description	Default
`ko_id`	Yes
`detail_level`	No		summary

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.5.0Oct 23, 2026

addedOutput schema / $defs / EntrySummary / properties / symbol

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Symbol"
+}

removedOutput schema / $defs / ErrorResult

Removed value: -{
-  "description": "Structured error returned by a tool when the KEGG API fails.\n\nA tool returns this instead of raising so the model can reason about\nthe failure and decide whether to retry, change inputs, or give up.\nA point lookup that receives a 404 uses code ``not_found``; an empty search\nremains a successful result with no items.",
-  "properties": {
-    "code": {
-      "default": "kegg_api_error",
-      "title": "Code",
-      "type": "string"
-    },
-    "error": {
-      "title": "Error",
-      "type": "string"
-    },
-    "hint": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "title": "Hint"
-    },
-    "path": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "title": "Path"
-    },
-    "retryable": {
-      "default": false,
-      "title": "Retryable",
-      "type": "boolean"
-    },
-    "status": {
-      "anyOf": [
-        {
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "title": "Status"
-    }
-  },
-  "required": [
-    "error"
-  ],
-  "title": "ErrorResult",
-  "type": "object"
-}

addedOutput schema / $defs / KOInfo / properties / genes_truncated

Added value: +{
+  "default": false,
+  "title": "Genes Truncated",
+  "type": "boolean"
+}

addedOutput schema / $defs / Reference / properties / sequence

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sequence"
+}

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "$ref": "#/$defs/KOInfo"
-  },
-  {
-    "$ref": "#/$defs/EntrySummary"
-  },
-  {
-    "$ref": "#/$defs/ErrorResult"
-  }
-]New value: +[
+  {
+    "$ref": "#/$defs/KOInfo"
+  },
+  {
+    "$ref": "#/$defs/EntrySummary"
+  }
+]

First observedv0.1.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact – that 'full' performs a complete flat-file parse (i.e., a much larger, heavier response than the compact default). It says nothing about KEGG rate limits, failure modes for unknown KO IDs, or response size.

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?

One-sentence purpose followed by a compact Args block; front-loaded and free of filler. The Args block partially restates the schema, but it earns its place because the schema itself has zero descriptions.

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?

An output schema exists so return values need not be described, and annotations cover safety; what remains is well served by the parameter explanations. The one meaningful gap is routing: an agent cannot tell from this description whether to search first or call directly, and sibling search_ko_entries is the obvious candidate.

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 description coverage is 0%, so the description carries the full burden and largely does: it defines ko_id with a concrete example ('K00844' for hexokinase) and explains both enum values of detail_level, including which is the default. It stops short of quantifying what 'compact' vs 'complete' actually returns.

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: 'Get detailed information for a KEGG Orthology (KO) entry,' naming the KO identifier format with an example. It is clearly distinct from lookup-ish siblings by the word 'detailed', though it never names search_ko_entries as the discovery path.

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

Usage Guidelines2/5

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

No statement of when to use this versus search_ko_entries or batch_entry_lookup, and no prerequisite such as 'KO IDs must be obtained from search_ko_entries first.' The only usage-adjacent content is the detail_level tradeoff, which is parameter guidance rather than tool selection guidance.

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