Skip to main content
Glama

forex.mobile broker data

Recommend brokers for a country

recommend_broker
Read-onlyIdempotent

Top 3 brokers for a trader's country, the same answer as /api/v1/recommend: forex.mobile's ranking, limited to brokers whose own restricted-countries list was read and does not exclude the country, ordered by the chosen priority. priority: spreads (lowest published spread, the default), deposit (lowest published minimum), regulation (most top-tier retail licences); anything else uses the overall ranking. 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

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": {
      "country": "<country>"
    },
    "name": "recommend_broker"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry slug (e.g. uae, vietnam, us) 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
priorityNospreads | deposit | regulation (default spreads; anything else: overall ranking)
experienceNoEchoed back; it does not change the order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, and the description adds substantial context beyond them: the restricted-countries filtering rule, the provenance of scores (named reviewers, published terms, regulator records, Trustpilot), and an explicit disclaimer that no live spreads or execution are measured. The methodology link further supports verification.

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 key output is front-loaded in the first clause and every subsequent clause carries information about filtering, ordering, or score provenance. It is a dense, semicolon-chained paragraph rather than cleanly structured sentences, and the trust disclaimer, while useful, lengthens it noticeably.

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?

For a three-parameter read tool with no output schema, the description covers the ranking logic, ordering, score scale (out of 5), and data provenance — enough to interpret results. It does not sketch the response shape (e.g. which fields accompany each broker), which is the only notable gap.

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 100%, so the baseline is 3, but the description adds real meaning for priority — 'spreads' = lowest published spread (default), 'deposit' = lowest published minimum, 'regulation' = most top-tier retail licences, anything else = overall ranking. The third parameter, experience, is never mentioned in the description, leaving its no-op behavior to the schema alone.

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?

States a specific verb and resource ('Top 3 brokers for a trader's country') plus the exact ranking semantics ('the same answer as /api/v1/recommend'). The scope constraints — limited to brokers whose restricted-countries list was read and does not exclude the country — make it unmistakable against siblings like list_brokers or compare_brokers.

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 use case is clearly framed (recommendation for a trader's country) and the priority options with their defaults are spelled out, including the fallback for unrecognized values. It stops short of explicitly naming when to prefer compare_brokers or list_brokers instead, so no exclusion guidance is given.

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