Skip to main content
Glama
Sign In
trackr

trackr

by jakuubkoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

login

Authenticate to a ForexTrackr firm with an API key, validate the key and URL, and save them locally under a firm name as the active firm.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>"
    },
    "name": "login"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe ForexTrackr address, e.g. https://trackr.example.com (needed for a new firm)
firmNoFirm name to save it under (default: the active firm, or firm1)
api_keyYesThe API key, starting with trk_

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does disclose real behavior: the key and URL are validated ('checked') and persisted on this machine under a firm name, and that firm becomes active. That is meaningful side-effect disclosure for a credential-handling tool. It stops short of covering failure modes, whether existing saved credentials are overwritten, or whether other tools require this call first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the core action plus its credential source are front-loaded before the persistence note. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description must cover returns and safety; it covers the persisted state and active-firm effect well. What remains thin is what the agent sees back (success/failure signal) and how this interacts with switch_firm logout flows, but nothing essential to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters including defaults for firm and the purpose of url. The description corroborates the trk_ prefix and the 'url needed for a new firm' nuance but adds no syntax, format, or edge-case detail beyond what the schema provides — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Sign in to a ForexTrackr firm with an API key') plus the precondition for obtaining the credential. The closing clause 'becomes the active firm' distinguishes it from switch_firm and logout in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It establishes the prerequisite (an admin-created trk_ key from Admin Settings > User Management > API Keys) and notes that url is needed for a new firm, which implicitly tells the agent when this call is appropriate. However, it never says when NOT to use it — e.g. that an already-authenticated session should use switch_firm instead, or that logout ends a session.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools