SourceVahti
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 |
|---|---|
| search_indicatorsA | Search precisely defined indicators and expose all valid rate variants. |
| get_observationsB | Return a normalised series only after resolving its full definition. |
| get_latest_observationB | Return the latest observation with definition and full provenance. |
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
The three tools target distinct operations: searching indicators, retrieving full observation series, and fetching the latest observation. Search vs. retrieval is clear, and the latest observation is a specific convenience function, though it could be seen as a subset of get_observations.
All tool names follow the verb_noun pattern consistently: search_indicators, get_observations, get_latest_observation. The verbs (search/get) and noun phrases are clear and predictable.
With only 3 tools, the server is minimal but well-suited for a focused data-access purpose. It feels slightly thin but not under-scoped, and each tool serves a distinct and necessary function.
The domain is read-only indicator/observation data access. The tools cover searching for definitions, retrieving time series, and getting the latest value. A possible gap is a direct 'get_indicator' by exact ID, but search_indicators likely handles that. Core workflows appear covered.