Skip to main content
Glama

FX rate normaliser

submit_fx_rate_normaliser
Idempotent

Convert a column of amounts to a base currency using a supplied rate table. When amounts in mixed currencies must be brought to one base. Do not choose this when live or date-specific rates are required. Example requests: Convert these amounts to USD. | Normalise this column to a single currency. | Apply this rate table to my rows.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_fx_rate_normaliser"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotent, non-destructive, closed-world behaviour, so the bar is lower. The description usefully implies offline, rate-table-driven conversion with no external rate lookup. It omits the priced-capability workflow entirely: quote_id, accepted_price and authorized_by are required/expected by the schema, yet nothing in the description tells the agent a quote must be obtained first.

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?

Front-loaded with the core action, followed by a use condition and an exclusion. The second sentence is a fragment and the three example requests are near-redundant with the opening line, but no sentence is actively harmful.

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

Completeness3/5

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

Return values are covered by the output schema, but this is a priced job submission with a required authorized_by and a quote_id that the service rejects if missing, and the description never surfaces that workflow. For a nested 4-parameter paid capability, that is a meaningful completeness gap.

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 75%, so the baseline is 3. 'Using a supplied rate table' gives the rates input some meaning, but the description says nothing about rows, base_currency, or the quote/pricing parameters that are likely to trip an agent up.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: convert a column of amounts to a base currency using a supplied rate table. 'Using a supplied rate table' implicitly separates it from a live-rate tool, though no sibling such as submit_unit_conversion_library is named.

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?

Gives an explicit when ('amounts in mixed currencies must be brought to one base') and an explicit when-not ('live or date-specific rates are required'). It stops short of naming which tool to reach for instead, so the exclusion terminates without a routing target.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources