Skip to main content
Glama
Sign In
fxabsolute-mcp

fxabsolute-mcp

by varsansri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

fxa_instruments

List all FXAbsolute instruments with candle data, including bar counts, pip size, and field information, noting that volume is unavailable, to help you decide what to query.

Instructions

List every instrument FXAbsolute has candle data for, with bar counts and pip size. Call this first if you are unsure what is available. Also states plainly which fields exist — notably, this dataset has no volume.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses a key data limitation ('this dataset has no volume') and implies a read-only operation through 'List', which is valuable behavioral context beyond the schema.

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 just two sentences: the first states the core purpose and output, the second adds usage guidance and a data caveat. 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.

Completeness5/5

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

For a zero-parameter tool with no output schema, the description fully explains what the tool returns (instrument list with bar counts and pip size) and provides a notable data caveat. It is complete for an agent to decide when and how to use it.

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?

The tool has zero parameters, so the input schema is empty. The description doesn't need to explain parameters, and the baseline for zero-parameter tools is 4. The description's focus on output and data caveats is appropriate.

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 the specific verb 'List' and clearly identifies the resource ('every instrument FXAbsolute has candle data for') with output details (bar counts, pip size). This distinguishes it from sibling tools like fxa_candles, making its purpose unmistakable.

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 advises calling this tool first when unsure of available data, providing a clear usage context. It does not mention exclusions or alternatives, but the guidance is direct and actionable.

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