Universal Reference Resolver
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_referenceC | Resolves any external reference and retrieves its associated information from the authoritative 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 1 tool
There is only one tool, so there is no possibility of confusing it with another tool in the set. Its purpose is distinct by default.
The single tool follows a clear snake_case verb_noun pattern: resolve_reference. No inconsistent naming conventions are present.
A single tool is borderline thin for a server that claims to be a universal reference resolver. While one operation may be intentional, 1-2 tools often feels under-scoped for a broad domain.
The tool covers retrieval of information from an authoritative source, but there is no visible support for enumerating sources, batch resolution, error modes, or metadata. For a universal resolver, this leaves notable gaps that agents may need to work around.