phenoforge
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_conceptA | Look up a single ICD-10-CM concept by its exact billing code. Use this when the caller already has a specific code, e.g. :param concept_code: An exact ICD-10-CM code, e.g. |
| expand_hierarchyA | Expand an ICD-10-CM code to every code beneath it in the billing hierarchy. For example, expanding :param seed_code: An exact ICD-10-CM code to expand from, e.g. |
| search_conceptsA | Search ICD-10-CM concept names for a free-text clinical term or phrase. Combines lexical (BM25) and semantic (embedding) matching, fused by
reciprocal rank, so paraphrased or loosely-worded descriptions (e.g.
"sugar disease" for diabetes) are found even without shared exact
wording — always prefer this over guessing at exact terminology
yourself. Every returned concept is tagged :param query: Free-text search string, e.g. |
| find_curated_definitionA | Search the OHDSI Phenotype Library for a validated cohort definition. Use this FIRST for any population description that plausibly matches a
peer-reviewed phenotype (e.g. "type 2 diabetes", "diabetic ketoacidosis")
— a match here is :param query: Free-text population description.
:returns: The best-matching cohort's resolved ICD-10-CM concepts tagged
|
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 4 tools
Each tool occupies a distinct role: exact code lookup, hierarchy expansion, free-text concept search, and curated phenotype library lookup. Explicit cross-references such as 'not a search tool' and 'use this FIRST' make misselection unlikely.
All tool names follow a clear snake_case verb_noun pattern: lookup_concept, expand_hierarchy, search_concepts, find_curated_definition. The names are predictable and communicate their action on a target object.
Four tools is well-scoped for a narrow terminology and phenotype discovery server. Each tool maps to a distinct workflow step without redundancy or unnecessary bloat.
The core discovery workflows are covered: exact code lookup, free-text search, hierarchy expansion, and curated cohort lookup. Missing capabilities like ancestor navigation, batch lookup, or explicit concept set construction are workaround-able and do not severely undermine the stated purpose.