TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures

Forex Pip Value (Live)

workflow.run_forex_pip_value_live

Read-only

Value of 1 pip for a forex pair and position size, converted to a given account currency via a live FX rate: TrueFX for its 10 quoted majors (genuinely live tick data), frankfurter.app daily ECB reference rate as the fallback for every other currency (30 total). Precious-metal pairs (XAU, XAG, XPT, XPD) are refused with an error, because their pip and lot size differ by broker. Edge cases: same input rules as workflow.run_forex_pip_value; when no rate is found for the account currency, available is false and no figure is returned. The rate is a TrueFX tick or a daily ECB reference rate, not a dealer quote. Not covered: broker markups and fractional pips. Use when user asks "what's 1 pip worth in my account currency?" and the account currency differs from the pair's own quote currency (if it matches, workflow.run_forex_pip_value alone is enough, no live fetch needed). Returns everything workflow.run_forex_pip_value does, plus accountCurrency, pipValueAccount, fxRate, fxSource (truefx/frankfurter/identity), available (false + error if no rate could be found for that currency). If available is false, do not use any result field (computed figures and any verdict are null or empty), so read available first.

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": {
      "pair": "<pair>",
      "units": "<units>",
      "accountCurrency": "<accountCurrency>"
    },
    "name": "workflow.run_forex_pip_value_live"
  }
}

Input Schema

Name	Required	Description
`pair`	Yes	Currency pair in BASE/QUOTE format, e.g. "EUR/USD"
`units`	Yes	Position size in base-currency units
`accountCurrency`	Yes	3-letter account currency code, e.g. "GBP"

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint/destructiveHint, the description discloses the data sources and their quality tier (TrueFX live ticks for 10 majors vs. daily ECB reference for 30 currencies), that metals are rejected with an error, that a missing rate yields available=false with no figure, and that the rate is not a dealer quote. It also warns to read available first before consuming any computed field — exactly the kind of behavioral context annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical routing information is front-loaded and every sentence carries substance (sources, refusals, edge cases, return fields). It is dense and parenthetical-heavy, though, with several clauses packed into single sentences that could be split for faster scanning.

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?

With no output schema, the description fully compensates by enumerating the returned fields (accountCurrency, pipValueAccount, fxRate, fxSource with its truefx/frankfurter/identity values, available) and by specifying the failure state. For a 3-parameter read-only computation, nothing an agent needs to call it safely is missing.

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 already 100%, so the baseline is 3; the description still adds meaning by framing accountCurrency as the conversion target and indicating the identity case where it equals the pair's quote currency, and by noting input rules mirror workflow.run_forex_pip_value. It does not add format specifics beyond the schema, so not a 5.

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 a specific verb and resource — the value of 1 pip for a forex pair and position size, converted into an account currency via a live FX rate — and explicitly distinguishes itself from the sibling workflow.run_forex_pip_value by naming the live fetch as the differentiator.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('what's 1 pip worth in my account currency?') plus a routing rule: if the account currency matches the pair's quote currency, use workflow.run_forex_pip_value instead, no live fetch needed. It also states exclusions (precious-metal pairs are refused) and a fallback path (frankfurter when TrueFX has no rate).

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

All TradingCalc MCP: Options, Forex, Risk Stats, Prediction Markets, On-Chain & Crypto Futures tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.