Skip to main content
Glama

forex.mobile broker data

List brokers

list_brokers
Read-onlyIdempotent

List the forex brokers forex.mobile reviews, highest editorial score first, with score, published minimum deposit and lowest published spread, retail regulators, platforms, Trustpilot rating and an affiliateUrl. Optional filters: country (only brokers whose own restricted-countries list was read and does not exclude it), islamic (only brokers whose own site offers a swap-free account), maxMinDeposit (USD) and platform. Broker scores are forex.mobile's editorial ratings out of 5, written by a named reviewer from each broker's published terms, regulator records and Trustpilot ratings. Spreads, deposits and platforms are the figures each broker publishes; forex.mobile does not trade real money with brokers or measure live spreads or execution. Methodology: https://forex.mobile/methodology

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_brokers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoCountry slug (e.g. uae, vietnam, india) or two-letter ISO code. Slugs: uae, saudi-arabia, kuwait, egypt, india, australia, uk, canada, nigeria, south-africa, france, singapore, us-traders, vietnam, thailand, philippines, indonesia, malaysia, japan, hong-kong, pakistan, kazakhstan, mongolia, ghana, bangladesh, kenya, morocco, tanzania, brazil, colombia, germany, italy, spain, netherlands, sweden, switzerland, sri-lanka, qatar, mexico
islamicNotrue: only brokers whose own site says it offers an Islamic (swap-free) account
platformNoOnly brokers that list this platform, e.g. MT4, MT5, cTrader, TradingView
maxMinDepositNoOnly brokers whose published minimum deposit is at most this many US dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: results are sorted by editorial score, the country filter only includes brokers whose restricted-countries list was actually read, and scores are named-reviewer editorial ratings rather than live measurements. The data-provenance disclaimer (no real-money trading or live spread measurement) is exactly the kind of caveat structured fields 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 what-and-ordering comes first, then filters, then provenance, then the methodology link — a sensible front-loaded order with no filler. The provenance sentences are long, but each carries non-obvious information about how the ratings and spreads were sourced.

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 takes on the burden of describing return fields (score, min deposit, lowest spread, regulators, platforms, Trustpilot, affiliateUrl) and it does so completely, alongside filter semantics and data caveats. An agent has everything needed to call this correctly.

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 description coverage is 100%, so the baseline is 3, but the description reinforces the filter semantics in prose (maxMinDeposit in USD, islamic means a swap-free account on the broker's own site) and adds the nuance that a country match requires the broker's restricted-countries list to have been read and not to exclude it.

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?

Opens with a specific verb+resource ("List the forex brokers forex.mobile reviews") and enumerates the returned fields and sort order, so the agent knows exactly what it gets back. It never names a sibling such as get_broker or recommend_broker, so differentiation is only implied by the plural 'list' framing.

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 explains the optional filters and their meaning, which implies 'use this to browse/filter the full broker set', but it gives no explicit when-to-use or when-not-to-use guidance against compare_brokers, get_broker or recommend_broker.

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