Skip to main content
Glama
Sign In
movmint-fx-mcp

movmint-fx-mcp

by nziacbdc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

capture_fx_quote

Execute an FX quote using its quote_id to complete a trade. Returns deposit address and transaction details. Quote valid for 30 seconds after generation.

Instructions

Capture (execute) a previously generated FX quote using its quote_id. The quote must not have expired (valid for ~30 seconds after generation). Returns transaction details including the deposit address for funding.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "capture_fx_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesThe quote_id returned from get_fx_quote

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Without annotations, the description carries the full burden. It discloses the critical expiration constraint and the return of transaction details including deposit address. It could mention the irreversible nature of execution, but the key traits are well-covered.

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 sentences, both front-loaded with essential information: action, condition, and return value. No superfluous words.

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 simple tool with one parameter and no output schema, the description covers purpose, prerequisite, constraint, and return value. It is complete.

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 repeats the source of quote_id (get_fx_quote) already in the schema description, adding no new parameter semantics.

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 clearly states the action 'Capture (execute)' and the resource 'previously generated FX quote using its quote_id', effectively differentiating from sibling get_fx_quote.

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 notes the expiration condition (~30 seconds) and the required prior step (generating a quote), providing clear context. It does not explicitly list when not to use, but the sibling relationship provides alternatives.

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