Skip to main content
Glama
enesjakozh
EdenYavin

OSV

by EdenYavin
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_ecosystems

Retrieve supported package ecosystems and their programming languages to identify correct names for vulnerability queries in the OSV server.

Instructions

Get all supported ecosystems. An ecosystem is a package manager or repository for a specific language.

Returns:
Dictionary of ecosystems with the key being the ecosystem name and the value being the programming language / OS.

To use the ecosystem name in the query_package_cve function, you must use the exact ecosystem name as it is in the dictionary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.py:105-116 (handler)
    The main handler function for the 'get_ecosystems' tool, decorated with @mcp.tool() for registration in the MCP server. It returns a dictionary of supported ecosystems.
    @mcp.tool()
def get_ecosystems():
    """
    Get all supported ecosystems. An ecosystem is a package manager or repository for a specific language.

    Returns:
    Dictionary of ecosystems with the key being the ecosystem name and the value being the programming language / OS.

    To use the ecosystem name in the query_package_cve function, you must use the exact ecosystem name as it is in the dictionary.
    """
    return {"PyPI": "python", "npm": "javascript", "RubyGems": "ruby", "Maven": "java", "NuGet": "c#"}
  • src/server.py:105-105 (registration)
    The @mcp.tool() decorator registers the get_ecosystems function as an MCP tool.
    @mcp.tool()

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully describes the return format ('Dictionary of ecosystems with the key being the ecosystem name and the value being the programming language / OS') and a critical behavioral constraint ('you must use the exact ecosystem name as it is in the dictionary'). However, it doesn't mention potential limitations like rate limits or authentication requirements.

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 perfectly structured with three focused sentences: purpose definition, return format specification, and usage guidance. Every sentence adds essential information with zero redundancy or unnecessary elaboration.

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-parameter tool with no annotations and no output schema, the description provides excellent context about the return format and how to use the output with sibling tools. The only minor gap is the lack of information about potential error conditions or system limitations, but this is reasonable given the tool's simplicity.

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 has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't waste space discussing nonexistent parameters, maintaining focus on the tool's purpose and output.

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 clearly states the tool's purpose with specific verb ('Get') and resource ('all supported ecosystems'), and provides a precise definition of what an ecosystem is ('package manager or repository for a specific language'). It distinguishes this from sibling tools by focusing on ecosystem retrieval rather than CVE queries.

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 states when to use this tool ('To use the ecosystem name in the query_package_cve function') and provides a clear alternative context by naming the specific sibling tool where the output is needed. It establishes a prerequisite relationship between tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EdenYavin/OSV-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server