crc-lnm-medical-agent
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthcheckA | Report the installed package identity and canary transport profile. |
| describe_deploymentB | Describe the deliberately limited behavior of this deployment stage. |
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 2 tools
The two tools are clearly distinct: one reports health/status information, the other describes the deployment's behavior. There is no overlap in their purposes.
Naming styles are inconsistent: 'healthcheck' is a single word noun, while 'describe_deployment' follows the verb_noun snake_case pattern. This lack of a consistent convention makes the set feel uncoordinated.
With only two tools, the set is on the thin side, but the explicit mention of a 'deliberately limited behavior' suggests this small count is intentional for a staging environment. Still, it is borderline for a typical server.
Despite the server name indicating a medical agent, the provided tools only cover operational metadata (healthcheck and deployment description) with zero medical domain functionality. The surface is severely incomplete for any meaningful medical workflow.