Skip to main content
Glama

forex.mobile broker data

Get broker

get_broker
Read-onlyIdempotent

One broker's full record: editorial score, published costs and deposit, retail regulators, platforms, pros and cons from the review, register-sourced notes, Trustpilot rating, review URL and affiliateUrl. 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": {
      "key": "<key>"
    },
    "name": "get_broker"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesBroker key, one of: exness, xm, vantage, axi, tickmill, fpmarkets, roboforex, avatrade, icmarkets, oanda, plus500, etoro, deriv

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description still adds real behavioral context beyond them: the provenance of the editorial scores, the fact that spreads/deposits/platforms are broker-published figures, and the explicit caveat that forex.mobile does not trade real money or measure live spreads or execution. Only the methodology link and the score semantics go further; it doesn't describe error behavior for an unknown key.

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?

Contents are front-loaded in the first sentence, with provenance and methodology caveats following in logical order. The middle sentence is dense but each clause conveys distinct information; only the methodology URL is arguably filler for an agent that cannot fetch it.

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?

There is no output schema, so the description carries the burden of describing the return payload, and it does so field-by-field. Combined with the data-provenance caveat, an agent has everything needed to call it and interpret the result.

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% and the single required parameter `key` already carries the enumerated allowed values in the schema. The description adds no additional meaning about the key, so the baseline 3 applies.

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?

The description opens with a concrete verb-plus-resource framing ("One broker's full record") and enumerates the payload: editorial score, costs, deposit, regulators, platforms, pros/cons, Trustpilot, review URL, affiliateUrl. That makes it clearly a single-broker detail fetch rather than a list or comparison, though it never names the siblings it differs from.

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?

Usage is only implied: an agent can infer this is for pulling detail on one known broker key, versus list_brokers or compare_brokers. There is no explicit when-to-use statement, no exclusion, and no guidance on what to do if the key isn't one of the listed brokers.

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