bertron-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geosearchC | Find genomic and environmental samples near any location on Earth using latitude/longitude coordinates |
| health_checkA | Verify that the BERtron API and database are online and responding correctly |
| bbox_searchB | Find all samples within a rectangular geographic region defined by corner coordinates |
| entity_lookupA | Get comprehensive metadata for a specific biological sample or dataset using its unique identifier |
| advanced_queryB | Execute sophisticated searches with custom filters, field selection, pagination, and sorting options |
| search_by_sourceB | Find samples and datasets from specific DOE research facilities (EMSL, ESS-DIVE, JGI, NMDC, MONET) |
| search_by_typeA | Find specific types of biological or environmental data (samples, sequences, biodata, taxa) |
| search_by_nameC | Search through sample names, project titles, and descriptions using text patterns and keywords |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
The specific search tools (bbox_search, geosearch, search_by_name, etc.) each target distinct criteria, but the generic advanced_query tool overlaps with all of them, creating potential confusion for tool selection.
Tool names use a mix of patterns: adjective_noun (advanced_query), abbreviation_noun (bbox_search), noun_verb (entity_lookup, health_check), and verb_preposition_noun (search_by_name, etc.), with no consistent convention.
8 tools is an appropriate scope for a query-focused data server; not too many or too few.
The server covers a wide range of query methods (text, location, facility, type) and includes a health check, but lacks tools for discovering available sources or types without a specific query, and does not include any write operations.