financial-evidence
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 |
|---|---|
| financial_evidence_topicsA | List supported topics and their fixed public raw-JSON routes without network access. |
| financial_evidence_routeA | Resolve one or more financial research topics to fixed public raw-JSON sources without fetching them. |
| financial_evidence_fetchB | Fetch bounded untrusted read-only JSON from fixed LiquiLens, Undertow, Seiche, and Palimpsest routes. Status reports transport only; evidence is not evaluated and Evidence Carrier verification is not performed. |
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 fetch tool is clearly distinct, but topics and route overlap somewhat since topics already lists the raw-JSON routes. The distinction is mostly clear: topics returns the full catalog, while route resolves a specific topic to its sources.
All tool names share the consistent financial_evidence_ prefix and use straightforward lowercase snake_case. The final words topics, route, and fetch are simple and predictable.
Three tools is well-scoped for the stated purpose of listing, resolving, and fetching financial evidence sources. Each tool serves a distinct step in the workflow without unnecessary bloat.
The topics -> route -> fetch pipeline is complete for transport-level evidence retrieval. Missing verification or evaluation is intentional and explicitly disclaimed, but the server name might lead agents to expect some evidence assessment capability.