Skip to main content
Glama
currencytransfer

CurrencyTransfer MCP Server

Official

create_rsi_alert

Creates an RSI-based market order alert for currency pairs, triggering when the RSI indicator reaches a target. Supports auto-booking, split tranches, and conditional rates.

Instructions

Creates an RSI (MOEX) market order. Triggers when the RSI indicator for the currency pair reaches target_rsi. Optionally auto-books the trade and splits the total amount into tranches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sell_currencyYes3-letter currency code the client has (e.g. EUR)
buy_currencyYes3-letter currency code the client wants (e.g. USD)
sideYes
amountYesTotal amount
target_rsiNoRSI threshold to trigger (default: 70)
bookNoAuto-book when RSI threshold is reached (default: false)
reasonNoRequired if book=true
expiration_dateNoExpiry date YYYY-MM-DD (max 30 days)
delivery_dateNo
minimal_rateNoMinimum acceptable rate — trade only books if RSI AND rate conditions are both met
book_remaining_amount_on_expirationNoIf true, books remaining unexecuted amount when the alert expires
beneficiary_uuidNoAssign a beneficiary — auto-creates a payment when trade is booked
payment_referenceNoRequired if beneficiary_uuid is provided
payment_purposeNoRequired if beneficiary_uuid is provided
splitsNoSplit total amount into tranches, each executed when RSI triggers
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the trigger condition and optional auto-booking/splitting but does not disclose side effects, permissions, or behavior in edge cases (e.g., partial fills, expiration handling).

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, front-loaded with the core purpose, no wasted words. Efficient and clear.

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?

Given the absence of an output schema and 15 parameters, the description covers the primary behavior but lacks details about expiration, beneficiary integration, and conditional booking rules. Some of this is in parameter descriptions, but the description could be more comprehensive.

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 high (87%), but the description adds meaningful context by explaining that the alert triggers on RSI, auto-books, and splits into tranches. This goes beyond the schema's individual parameter descriptions.

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 tool creates an RSI market order triggered by the RSI indicator, with optional auto-booking and splitting. It uses a specific verb and resource, and distinguishes from sibling tools like create_rate_alert and create_trade.

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

Usage Guidelines3/5

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

The description implies usage for RSI-based triggers but does not explicitly say when to use this tool versus alternatives (e.g., create_rate_alert). No when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/currencytransfer/mcp-currencytransfer'

If you have feedback or need assistance with the MCP directory API, please join our Discord server