Skip to main content
Glama

Check Broker Trustworthiness

is-broker-trusted
Read-only

Retrieves information to determine whether a broker is legitimate or a scam. This tool can look up brokers using either their company name or website URL. It returns verification data, scam reports, regulatory status, and trustworthiness indicators to help assess the broker's credibility. Use this tool when users ask about broker reliability, safety, legitimacy, or want to verify if a specific broker is trustworthy before investing or trading.

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": {
      "query": "<query>"
    },
    "name": "is-broker-trusted"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA string containing either the broker's company name OR the broker's website domain as provided by the user. If providing a website, use only the domain name with TLD (e.g., 'example.com' not 'https://www.example.com' or 'https://example.com/page'). For company names, provide the full or commonly known name of the broker (e.g., 'XYZ Trading' or 'ABC Brokers').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already declares the safety profile, so the description only needs to add context — and it does, enumerating the returned content ('verification data, scam reports, regulatory status, and trustworthiness indicators'). That is valuable since no output schema exists. It omits any caveat about data source, freshness, or what happens on an unknown broker, which keeps it from a 5.

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 how are front-loaded in the first two sentences, and the usage trigger comes last where it belongs. There is mild redundancy between 'trustworthiness indicators to help assess the broker's credibility' and the earlier 'legitimate or a scam', but nothing is wasted outright.

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 single-parameter, read-only lookup with no output schema, the description covers what it takes, what it returns conceptually, and when to call it. What remains unaddressed is how to interpret weak or missing results — minor for this tool's complexity.

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 schema itself spells out the domain-vs-name formatting rules in detail. The description only restates that either a company name or website URL is accepted, adding no syntax or edge-case meaning beyond the schema. 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 specific verb and resource — 'Retrieves information to determine whether a broker is legitimate or a scam' — and the lookup modality (company name or website URL) is stated outright. It does not explicitly contrast itself with the sibling is-broker-available-in-country-tool, though the purposes are obviously distinct.

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 final sentence gives concrete trigger conditions: broker reliability, safety, legitimacy, or verification before investing/trading. It gives no explicit exclusions or named alternatives, so it sits at 'clear context, no exclusions' rather than full when/when-not guidance.

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