OpenGenes MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| opengenes_get_schema_infoC | Get information about the database schema |
| opengenes_example_queriesB | Get a list of example SQL queries |
| opengenes_db_queryB | Query the Opengenes database that contains data about genes involved in longevity, lifespan extension experiments on model organisms, and changes in human and other organisms with aging. Before caling this tool the first time, always check tools that provide schema information and example queries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_db_prompt | Get the database prompt that describes the OpenGenes database schema and usage guidelines. This resource contains detailed information about: - Database tables and their schemas - Column enumerations and valid values - Usage guidelines for querying the database - Examples of common queries Returns: The complete database prompt text |
| get_schema_summary | Get a summary of the OpenGenes database schema. Returns: A formatted summary of tables and their purposes |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: one queries the database, one provides example queries, and one gives schema information. An agent can easily tell them apart based on their specific functions.
All tools follow a consistent 'opengenes_' prefix with descriptive suffixes (_db_query, _example_queries, _get_schema_info), using snake_case uniformly. This predictable pattern enhances readability and usability.
With only 3 tools, the set feels thin for a database query server, as it lacks operations like data manipulation (e.g., insert, update) or advanced query features. However, it covers basic query support adequately for its stated purpose.
The tools provide essential query, example, and schema functions, but there are notable gaps such as no data modification tools (e.g., create, update, delete) or specialized query filters. This limits the server's ability to handle full database workflows.