kegg-mcp-server

get_glycan_info

Read-onlyIdempotent

Retrieve detailed information for a KEGG glycan entry by ID, with summary or full flat-file parse options.

Instructions

Get detailed information for a KEGG glycan entry.

Args: glycan_id: KEGG glycan ID (e.g. 'G00001'). detail_level: 'summary' (default, compact) or 'full' (complete flat-file parse).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "glycan_id": "<glycan_id>"
    },
    "name": "get_glycan_info"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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 / Reference / properties / sequence

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

changedOutput schema / properties / result / anyOf

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

First observedv0.1.0Jul 29, 2026

TDQS

A3.8/5.0

Behavior4/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 bar is low. The description still adds real value by explaining what detail_level actually changes ('summary' compact vs 'full' complete flat-file parse), which is a payload-size tradeoff the annotations cannot convey. It does not cover invalid-ID behavior, but that is a minor gap here.

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 one-line purpose is front-loaded and the Args block is scannable with zero filler. Slight redundancy between 'detailed information' and 'full (complete flat-file parse)', but nothing that wastes real space.

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, the description need not explain return values, and annotations cover the safety profile. Combined with parameter documentation, an agent has everything needed to call it correctly; only the sequencing relative to search_glycans is left implicit.

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 burden and does so: it gives the expected glycan_id format with a concrete example ('G00001') and spells out both enum values plus the default. The only omission is validation or error expectations for a malformed ID.

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 gives a specific verb ('Get detailed information') and resource ('a KEGG glycan entry'), which clearly separates it from the sibling search_glycans. It stops short of naming that sibling explicitly, but the get-vs-search distinction is inferable from the wording.

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 context is only implied: an agent can guess this is the detail-fetch step that follows search_glycans, but the description never states that or names any alternatives. No exclusions or prerequisites are given.

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