Skip to main content
Glama
florinel-chis

oanda-mcp

list_account_instruments

Read-only

List tradeable instruments on your OANDA account, including currency pairs, CFDs, and metals. Get precision details like pip location and display precision to set order prices and sizes.

Instructions

List instruments tradeable on the configured account.

Returns {"instruments": [...]} where each entry has name (e.g. EUR_USD), type (CURRENCY, CFD, or METAL), displayName, pipLocation (power-of-ten exponent of one pip: -4 means a pip is 0.0001), displayPrecision (the number of decimal places order prices must be formatted to — use it for the price of LIMIT/STOP orders or the API rejects them with a PRICE_PRECISION error), tradeUnitsPrecision (decimal places allowed in order units), minimumTradeSize (decimal string), marginRate (decimal string; the margin required per unit, e.g. "0.05" = 20:1 leverage), and maximumOrderUnits (decimal string).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of instruments to return.
instrumentsNoOptional instrument names to look up, e.g. ['EUR_USD', 'DE30_EUR']. Omit to list every tradeable instrument on the account.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds valuable behavioral context beyond annotations, such as the meaning of pipLocation, the requirement to use displayPrecision for order prices to avoid PRICE_PRECISION errors, and marginRate as leverage. This goes beyond simple return format.

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 description is front-loaded with the main action and then provides a structured, detailed breakdown of the returned fields. Each statement earns its place, though it is longer than necessary for a simple list tool. It is not wasteful, but not maximally concise.

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

Completeness4/5

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

The tool has an output schema, so the description need not explain return values, but it does so thoroughly with field semantics and practical usage tips. Given the two optional parameters and readOnly annotation, the description is complete enough for an agent to invoke correctly, though it omits edge cases like pagination or error behavior.

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 100% for both 'limit' and 'instruments'. The description does not add any additional parameter semantics beyond what the schema already provides, so the baseline of 3 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 clearly states 'List instruments tradeable on the configured account', using a specific verb and resource. It distinguishes from sibling tools by focusing on account instruments, not accounts, summaries, or trades.

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 provides clear context for use: listing tradeable instruments for the configured account. It does not explicitly mention alternatives or exclusions, but the purpose is self-evident given the tool name and sibling context, earning a 4 rather than a 5.

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/florinel-chis/oanda-mcp'

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