Skip to main content
Glama

forex.mobile broker data

Forex glossary

glossary_term
Read-onlyIdempotent

Definition of a forex term from the forex.mobile glossary (e.g. pip, spread, leverage, swap). Without a term, lists every term slug with its one-line definition.

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": "glossary_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoTerm slug, e.g. pip, margin-call, stop-loss

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. Beyond that, the description adds the genuinely useful behavioral detail of what happens when the optional term is omitted (enumerating every slug with a one-line definition), which the annotations do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the primary function and illustrative examples come first, then the default behavior with no argument. No filler or redundancy.

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?

For a one-optional-parameter read-only lookup with full annotation coverage and no output schema, the description covers both invocation modes and what each yields. Nothing needed to call it correctly is missing.

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. The description goes beyond it by clarifying the empty-parameter semantics of the optional term argument and by illustrating accepted slug forms, which meaningfully reduces ambiguity about omission.

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 pair: it returns the definition of a forex term from a named glossary, with concrete examples (pip, spread, leverage, swap). It also covers the no-argument mode, so an agent knows exactly what the tool returns in either case.

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 description makes the two usage modes explicit: pass a term slug to define one term, omit it to enumerate all slugs. It doesn't name a sibling or state exclusions, but the domain is distinct enough from the broker/rate siblings that the intended context is clear.

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