Skip to main content
Glama

find_databases

Identify relevant biological databases by searching with keywords like gene, pathway, or disease. Returns 1-3 scoped candidates for efficient workflow.

Instructions

Database discovery — REQUIRED first step for any TogoMCP workflow.

Always call this BEFORE get_MIE_file() or run_sparql(). Pass any search terms you have (gene, pathway, drug target, variant, organism, disease, enzyme class, etc.) as keywords. Returns 1–3 candidate databases scoped to your terms — much more efficient than browsing the full catalog.

Workflow:

  1. find_databases(keywords=[...]) — identify 1–3 relevant databases.

  2. get_MIE_file(database) — learn each candidate's schema and SPARQL idioms.

  3. run_sparql() — query with the discovered structured properties.

Common keywords to try: "MANE" (Ensembl), "drug targets" (ChEMBL), "clinical variants" (ClinVar), "pathways" (Reactome), "variants" (gnomAD), "ortholog" (OMA), "expression" (Bgee).

If you have no search terms and want to browse the full catalog instead, see list_databases() — that tool is supplementary, not a substitute for this one.

Returns: JSON string: a bare array of dicts {database, title, matched_keywords, categories, snippet} (or description when verbose=True). Sorted by number of matched keywords descending, then alphabetically by database name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchNo'any' returns DBs matching at least one keyword (OR); 'all' requires every keyword to match (AND).any
verboseNoIf True, return the full description; if False (default), return a short snippet around the first match.
categoryNoCategory filter (substring, case-insensitive). Call list_categories() to see the available set.
keywordsNoKeyword or list of keywords (case-insensitive substring match against title, description, and the database's curated keywords field).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so description carries full burden. It describes return format (JSON array with specific fields), sorting behavior (by matched keyword count), and scope (1–3 databases). Missing information on permissions or side effects, but these are minimal for a search 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?

Description is well-structured with clear sections: purpose, workflow, keyword examples, alternatives, and return format. It is somewhat long but every sentence adds value. Front-loaded with the most critical usage instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's 4 parameters (all with schema coverage), an output schema described in text, and a straightforward purpose, the description is complete. It covers workflow, inputs, outputs, and relationship to sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds workflow context and keyword examples but does not significantly enhance understanding of parameters beyond the schema descriptions (e.g., match, verbose, category).

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 it is a 'Database discovery' tool, explicitly distinguishing it from sibling tool 'list_databases' as the required first step. It specifies the action: identify 1–3 candidate databases based on keywords.

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?

Includes explicit workflow steps: call before get_MIE_file() and run_sparql(). Provides when-not-to-use guidance: use list_databases if no search terms. Gives common keyword examples, aiding correct invocation.

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/dbcls/togomcp'

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