eggnog-mcp

list_downloads

Retrieve URLs and descriptions for bulk-downloadable eggNOG 7 files, including protein sequences, orthologous group info, phylogenetic trees, and taxonomy data.

Instructions

List downloadable data files from the eggNOG 7 database.

Returns a list of all bulk-downloadable files (protein sequences, OG info, phylogenetic trees, taxonomic info, etc.) with their URLs and descriptions.

Returns

str JSON string with download file information.

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": "list_downloads"
  }
}

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.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses what the call returns (files with URLs and descriptions) which is genuinely useful, but says nothing about read-only semantics, authentication, rate limits, or the size of the listing. Adequate but leaves clear gaps for an annotation-free tool.

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?

Purpose is front-loaded in the first sentence and the follow-up sentence adds real detail about returned content. The trailing numpydoc 'Returns' block restates what the output schema already declares, which is minor redundancy but not wasteful enough to hurt much.

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 no-argument listing tool with an output schema present, the description covers the essential purpose and return content. It identifies the database version (eggNOG 7), which is useful context an agent would otherwise lack.

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 there is nothing for the description to disambiguate; baseline for a parameterless tool is 4. No parameter-related misinformation is present.

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 and resource ('List downloadable data files from the eggNOG 7 database') and enumerates the content categories (protein sequences, OG info, trees, taxonomic info). It is unambiguous and does not overlap any sibling, though it never explicitly names a sibling to differentiate against.

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 only implied: an agent can infer this is the tool to call when it needs bulk-download URLs rather than a single record lookup. There is no explicit when-to-use statement, no mention of when NOT to use it, and no reference to alternatives like get_database_stats.

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

Deploy Server