Skip to main content
Glama
Sign In
fxabsolute-mcp

fxabsolute-mcp

by varsansri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

fxa_connect_chart

Connect to a trader's FXAbsolute chart by entering the 6-character pairing code to start answering questions directly in their chart panel.

Instructions

Pair with a trader's open FXAbsolute chart using the code shown in the AI tab of the backtester. Once connected, the trader can type or speak to you and you answer in their chart panel. Call this when the user gives you a pairing code, e.g. "connect to fxabsolute with code AB3K9P".

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": {
      "code": "<code>"
    },
    "name": "fxa_connect_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe 6-character pairing code from the chart.
agentNameNoHow to identify yourself in the trader's panel, e.g. "Claude Code".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 burden. It discloses the result of pairing ('the trader can type or speak to you and you answer in their chart panel') and the code source, but does not mention permissions, failure modes, or connection lifecycle, leaving gaps.

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 concise sentences: first states the action and source, second explains consequence and trigger. Every sentence earns its place with no redundancy.

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 simple connection tool with 2 params and no output schema, the description covers what it does, when to call, and the resulting state. It lacks explicit return/error info but is reasonably complete for the scenario.

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 baseline is 3. The description's example reinforces the 'code' parameter but adds no new meaning beyond the schema, and agentName is left as-is.

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?

The description uses a specific verb ('Pair') and resource ('trader's open FXAbsolute chart'), and includes an example call. It clearly states the action and trigger, making it distinct from sibling tools like fxa_disconnect_chart.

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?

Explicitly states when to call: 'Call this when the user gives you a pairing code' with a concrete example. It provides clear usage context but does not discuss exclusions or alternatives, so it stops short of a 5.

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