Skip to main content
Glama
Sign In
trackr

trackr

by jakuubkoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

logout

Forget a saved API key for a ForexTrackr firm to securely end a session or switch firms. Optionally specify the firm; defaults to the active one.

Instructions

Forget the saved API key of a ForexTrackr firm.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "logout"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoFirm to forget (default: the active firm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the core side effect: the persisted API key is removed, not just the session changed. It does not say whether the active firm/session survives, whether the action is reversible (re-login required), or what happens if no key exists.

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?

One short sentence with the resource and the destructive effect front-loaded; there is no filler and nothing is buried.

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?

For a one-parameter tool with a fully documented schema and no output schema, this is close to sufficient — the destructive effect is stated plainly. It falls short only on post-conditions (session state, re-authentication need) that matter for a credential-removal operation with no annotations to lean on.

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% and the single optional 'firm' parameter is already documented with its default. The phrase 'of a ForexTrackr firm' loosely reinforces that the parameter selects the firm whose key is dropped, but adds no format or behavior detail beyond the schema.

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

Purpose4/5

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

States a specific verb and object: 'Forget the saved API key' scoped to a ForexTrackr firm. That is concrete and distinguishable from login (which stores a key) and switch_firm (which changes the active firm), though the description never names those siblings explicitly.

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?

Usage is only implied by the name and the word 'Forget'. There is no statement of when to call this rather than switch_firm — e.g., that switching firms preserves the key while this removes it — and no note about prerequisites such as having a key already saved.

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