trackr
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRACKR_URL | No | ForexTrackr instance address for firm1 | |
| TRACKR_API_KEY | No | ForexTrackr API key for firm1 | |
| TRACKR_FIRM1_URL | No | ForexTrackr instance address for firm1 | |
| TRACKR_FIRM2_URL | No | ForexTrackr instance address for firm2 | |
| TRACKR_FIRM1_API_KEY | No | ForexTrackr API key for firm1 | |
| TRACKR_FIRM2_API_KEY | No | ForexTrackr API key for firm2 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Sign in to a ForexTrackr firm with an API key (trk_..., an admin creates it in Admin Settings > User Management > API Keys). The key and URL are checked and saved on this computer under the firm name, which becomes the active firm. |
| switch_firmA | List the ForexTrackr firms set up and which one is active, or switch every tool to another firm. Call it before answering about a firm other than the active one. |
| logoutA | Forget the saved API key of a ForexTrackr firm. |
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 maps to a single, clearly distinct session operation: authenticate (login), inspect/change the active firm (switch_firm), and clear credentials (logout). There is no realistic scenario where an agent could confuse these three actions.
All names are lowercase snake_case and verb-oriented (login, switch_firm, logout), so the pattern is readable and predictable. The only minor deviation is that login/logout are bare verbs while switch_firm uses verb_noun, but the convention is still coherent.
Three tools is small, but it is well matched to a narrow session/authentication scope where each tool earns its place. It would be thin only if the server were expected to expose broader ForexTrackr data operations, which the surface does not claim.
The full credential lifecycle is covered: authenticate, switch between firms (which also reports the active firm, avoiding a separate list tool), and forget credentials. Minor gaps are the absence of a standalone status/whoami check and any key-refresh or multi-key management operation, but agents can work around these via switch_firm.