eggnog-mcp

get_database_stats

Retrieve summary statistics for the eggNOG 7 database, including counts of annotated species, protein sequences, phylogenetic trees, and orthologous groups in the current release.

Instructions

Retrieve summary statistics of the eggNOG 7 database.

Returns the number of annotated species, protein sequences, phylogenetic trees, and orthologous groups in the current eggNOG release.

Returns

str JSON string with database statistics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_database_stats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about read-only/side-effect status, authentication, rate limits, or caching. The only behavioral hint is that figures reflect the 'current eggNOG release', which is thin for a tool with zero annotation coverage.

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?

Front-loaded with the core purpose and reasonably short, but the word 'Returns' is used three times across a prose sentence, an enumerated list, and a NumPy-style Returns block, creating redundant restatement of the same return information.

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 zero-argument, read-only statistics tool with an output schema present, the description covers what the tool does and what the payload contains. Given the output schema exists, the explicit Returns block is not strictly needed, and the absence of behavioral/annotation context is the only notable gap.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter semantics to document or omit.

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?

States a specific verb and resource (retrieve summary statistics of the eggNOG 7 database) and enumerates the exact contents of those statistics (species, sequences, trees, orthologous groups). No sibling tool (get_protein, get_orthologous_group, search_eggnog, etc.) does this, so the tool is unambiguously distinguishable.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or fallbacks. The only usage signal is implied by the verb 'Retrieve', leaving the agent to guess the context in which database-level statistics are wanted.

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

Deploy Server