kegg-mcp-server

get_database_info

Read-onlyIdempotent

Retrieve release information and statistics for a specified KEGG database to verify versions and assess content coverage before querying pathways, genes, compounds, or drugs.

Instructions

Get release information and statistics for a KEGG database.

Args: database: Database name (e.g. 'kegg', 'pathway', 'compound', 'drug', 'genome').

Input Schema

Name	Required	Description	Default
`database`	No		kegg

Output Schema

Name	Required	Description	Default
`entries`	No
`release`	No
`database`	Yes
`raw_info`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.5.0Oct 23, 2026

removedOutput schema / $defs

Removed value: -{
-  "DatabaseInfo": {
-    "properties": {
-      "database": {
-        "title": "Database",
-        "type": "string"
-      },
-      "entries": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "title": "Entries"
-      },
-      "raw_info": {
-        "title": "Raw Info",
-        "type": "string"
-      },
-      "release": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "title": "Release"
-      }
-    },
-    "required": [
-      "database",
-      "raw_info"
-    ],
-    "title": "DatabaseInfo",
-    "type": "object"
-  },
-  "ErrorResult": {
-    "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 / properties / database

Added value: +{
+  "title": "Database",
+  "type": "string"
+}

addedOutput schema / properties / entries

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Entries"
+}

addedOutput schema / properties / raw_info

Added value: +{
+  "title": "Raw Info",
+  "type": "string"
+}

addedOutput schema / properties / release

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

removedOutput schema / properties / result

Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/$defs/DatabaseInfo"
-    },
-    {
-      "$ref": "#/$defs/ErrorResult"
-    }
-  ],
-  "title": "Result"
-}

changedOutput schema / required

Previous value: -[
-  "result"
-]New value: +[
+  "database",
+  "raw_info"
+]

changedOutput schema / title

Previous value: -"get_database_infoOutput"New value: +"DatabaseInfo"

First observedv0.1.0Jul 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context that the return is release information and statistics, but it does not discuss permissions, rate limits, or other behavioral constraints beyond what annotations provide.

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?

The description is short, front-loaded, and structured with an Args section. The examples are useful rather than wasteful, though the formatting could be tightened further.

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?

For a simple one-parameter read-only tool with rich annotations and an output schema, the description is largely complete: it explains the purpose and gives database examples. The main remaining gap is explicit usage guidance versus sibling info tools.

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 must carry parameter meaning. It does so by explaining that 'database' is a database name and giving representative examples such as 'kegg', 'pathway', 'compound', 'drug', and 'genome', though it does not enumerate all allowed values or mention the default.

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 and resource: getting release information and statistics for a KEGG database. It distinguishes the tool from entry-level siblings by focusing on database-level release/statistics, but it does not explicitly name an alternative or contrast with get_pathway_info/get_compound_info despite overlapping database names.

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 purpose—use this when you need release/statistics for a database rather than detailed entry data. However, there is no explicit when-to-use, when-not-to-use, or alternate-tool guidance.

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