life-science-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchToolsB | Search across all life science sources by intent, keyword, or tag |
| getToolInfoB | Get full parameter schema for a specific tool on a source |
| callToolC | Execute a tool on a life science source |
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 3 tools
Each tool serves a distinct purpose: searching for tools, retrieving schema details, and executing tools. There is no overlap between these operations.
All tool names follow a consistent verb-noun camelCase pattern: searchTools, getToolInfo, callTool. The naming is uniform and predictable.
With only 3 tools, the server is minimal yet appropriately scoped for its role as a meta-server. It provides the essential discover, inspect, and execute operations without unnecessary bloat.
The server covers the full lifecycle for interacting with external life science tools: discover via search, understand via getToolInfo, and run via callTool. No obvious gaps in this proxy-like design.