Skip to main content
Glama
Sign In
trackr

trackr

by jakuubkoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

switch_firm

Switch all tools to another ForexTrackr firm or list configured firms and the active one before answering about a firm other than the active one.

Instructions

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.

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": "switch_firm"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoFirm to switch to; leave out to list the firms

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A4/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; it does disclose the important side-effect scope that a switch affects "every tool", which is real behavioral value. It says nothing about permissions, whether the switch persists across sessions, or what happens on an unknown firm name.

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 short sentences, the capability first and the calling instruction second. Nothing redundant, nothing padded.

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 exists, and the description does indicate what the list mode reveals (firms set up plus the active one), which is the key return-value fact. Error behavior for an invalid firm name and persistence of the switch are the only notable omissions for a one-parameter tool.

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 description coverage is 100% and the single optional parameter already documents "leave out to list the firms". The description restates that behavior but adds no syntax, casing, or validation detail beyond the schema, so the baseline 3 applies.

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 two concrete verbs on a concrete resource: list ForexTrackr firms and which is active, or switch every tool to another firm. The dual mode is unambiguous and cannot be confused with the auth-oriented siblings login/logout.

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

Usage Guidelines4/5

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

"Call it before answering about a firm other than the active one" is an explicit usage trigger, and the schema/description pair states that omitting the parameter lists rather than switches. No explicit exclusion cases are given, but the trigger condition is clear enough to route correctly.

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