Skip to main content
Glama

forex.mobile broker data

Compare brokers

compare_brokers
Read-onlyIdempotent

Side-by-side records for 2 to 5 brokers. With exactly two, also returns the same short verdict as /api/v1/compare, built from score, published minimum deposit, Trustpilot rating, platform count and Islamic-account availability. 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": {
      "keys": "<keys>"
    },
    "name": "compare_brokers"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesTwo to five broker keys

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

With annotations already covering read-only, idempotent and closed-world safety, the description goes further and discloses a genuinely non-obvious behavior: the verdict is returned only when exactly two keys are supplied, mirroring /api/v1/compare. It also explains how the scores are produced (editorial ratings out of 5 from named reviewers, published terms, regulator records, Trustpilot), clarifies that spreads/deposits/platforms are publisher-reported rather than measured, and links the methodology — exactly the provenance an agent needs to caveat results.

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 headline capability and the two-broker verdict rule are front-loaded, which is the right ordering. The closing methodology/disclaimer sentences are longer than strictly necessary for tool selection, though they do carry real transparency value; the description could shed a clause or two without losing meaning.

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?

There is no output schema, so the description must carry return-value expectations, and it does: side-by-side records plus a verdict composed from five named fields for the two-broker case. The internal structure of a 'record' is not itemized, but for a one-parameter comparison tool the coverage is close to sufficient.

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 coverage is 100% and the single 'keys' parameter already documents the 2-to-5 bounds and the valid broker key list. The description repeats the arity range but adds no new meaning such as ordering effects or duplicate handling, 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 names a specific operation on a specific resource ('Side-by-side records for 2 to 5 brokers'), and the arity constraint implicitly separates it from the single-broker get_broker sibling. It stops short of naming any sibling explicitly, so the agent must infer the distinction from cardinality alone.

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: the 2-to-5 arity tells the agent this is for multi-broker comparisons, and the 'exactly two' clause signals a special case. There is no explicit statement of when to prefer this over get_broker or recommend_broker, and no guidance on what to do for a single-broker lookup.

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