Skip to main content
Glama

Kegg

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description adds rich behavioral context beyond annotations: key-value storage, scoping by identifier, and persistence differences (authenticated vs anonymous 24h). Annotations are idempotentHint=true, and description confirms idempotent behavior. No contradictions.

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?

The description is concise (3 sentences) with a clear front-loaded purpose, then usage guidelines, then technical details. Every sentence adds value with zero waste.

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?

Given no output schema, the description explains behavior and storage semantics thoroughly. It could mention return value or error handling, but covers the core functionality completely for a storage tool.

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 coverage is 100%, and the description adds real-world examples for keys and values, enhancing understanding. While schema already documents params, the examples provide added semantic clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Save') and resource ('data the agent will need to reuse later'), with examples of use cases. It also distinguishes from sibling tools recall and forget, meeting the highest standard.

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

Usage Guidelines5/5

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

The description explicitly says when to use ('when you discover something worth carrying forward') and pairs with recall and forget for complementary actions. It also provides context on scoping and persistence, guiding the agent effectively.

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

All Kegg toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Most tools have clearly described distinct purposes, but several overlap: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all occupy neighboring query/discovery territory. The Polymarket and memory tool families, by contrast, are well differentiated.

Naming Consistency3/5

All names are snake_case and readable, but the set mixes verb-first names (ask_pipeworx, compare_entities, resolve_entity, validate_claim) with noun-phrase names (entity_profile, bet_research, recent_alerts, polymarket_arbitrage) and brand prefixes (pipeworx_*, polymarket_*). There is no consistent verb_noun pattern across the toolkit.

Tool Count2/5

34 tools is well beyond the heavy range, and the count is especially inappropriate because the server is named Kegg but only find, get_entry, and list_database relate to KEGG bioinformatics. The remaining 31 tools span unrelated domains (generic data research, prediction markets, memory, subscriptions, AI visibility, npm scanning), making the scope feel like several products merged into one.

Completeness2/5

As a KEGG server, the surface is severely thin: three read-only tools with no pathway mapping, sequence search, or cross-reference utilities. The Pipeworx research and Polymarket betting subsystems are more complete, but their presence under a Kegg server makes the overall surface incoherent rather than complete.

Resources