fxabsolute-mcp

fxa_set_thinking

Show or hide a thinking indicator in the trader's panel. Activate it before long lookups so the user knows you're working; it clears automatically when the reply is sent.

Instructions

Show or hide the thinking indicator in the trader's panel. Call with on:true before a long lookup so they know you are working. fxa_reply clears it automatically.

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": {
      "on": "<on>"
    },
    "name": "fxa_set_thinking"
  }
}

Input Schema

Name	Required	Description	Default
`on`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the transparency burden. It discloses that the indicator is automatically cleared by fxa_reply, which is a useful behavioral trait beyond the raw toggle. It could specify whether on:false also clears the indicator, but the phrase 'Show or hide' implies both states.

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?

The description is three sentences, each adding value: the action, the call pattern, and the clearing behavior. No filler or redundancy.

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

Completeness5/5

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

The tool is a simple boolean setter with no output schema. The description covers its purpose, usage context, and interaction with fxa_reply, making it complete for an agent to select and call correctly.

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

Parameters4/5

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

Schema coverage is 0% (the 'on' property has no description in the schema), so the description must compensate. It gives a concrete example ('on:true') and the first sentence clarifies that true means show and false means hide, though not explicitly stated. For a single boolean parameter, this is adequate.

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 opens with 'Show or hide the thinking indicator in the trader's panel,' which precisely identifies the action and target. This clearly distinguishes it from sibling tools like fxa_candles or fxa_reply, none of which manage this indicator.

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?

The description explicitly instructs to 'Call with on:true before a long lookup,' establishing a clear when-to-use scenario. It also mentions 'fxa_reply clears it automatically,' providing an interaction note with a sibling tool, though it does not explicitly enumerate exclusions.

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

Deploy Server