geomed_copilot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GEOMED_DEMO_MODE | No | Set to '1' to run the MCP server in synthetic demo mode | 0 |
| GEOMED_ANNOTATIONS | Yes | Path to HVAngleEst/datasets.csv | |
| GEOMED_PREDICTIONS | Yes | Path to line_predictions_medimageinsight.csv | |
| GEOMED_SPLIT_MANIFEST | Yes | Path to hvangle_results.json | |
| GEOMED_EVIDENCE_CATALOG | Yes | Path to the evidence catalog JSON file |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_geomed_capabilitiesA | Describe the GeoMed backend, measurements, and limitations. |
| list_available_casesC | List case identifiers accepted by the configured backend. |
| analyze_radiographB | Run geometry checks, retrieval, citations, and tool traces for a configured case ID. |
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 clearly distinct purpose: describing backend capabilities, listing available cases, and analyzing a specific radiograph. There is no overlap in functionality, making misselection unlikely.
All tool names follow a consistent verb_noun pattern: list_geomed_capabilities, list_available_cases, analyze_radiograph. The naming is uniform and predictable.
With only 3 tools, the set is tightly scoped for the stated purpose of interacting with a GeoMed backend for case analysis. Each tool earns its place, and the count is appropriate—neither too sparse nor excessive.
The tool surface covers the full expected workflow: understanding the backend's capabilities, selecting a case, and performing the analysis (which includes retrieval and citations). No additional operations seem necessary for the apparent read-only analysis domain.