Skip to main content
Glama
Sign In

FxSocket

by com.fxsocket
OverviewDiscussionsAdmin

Get symbol specification

get_symbol_info
Read-onlyIdempotent

Contract specification for one symbol at this account's broker, read live from its terminal: digits, contract size, tick size and value, minimum/maximum/step volume, stops level, current spread, swap rates, commissions and trading sessions. symbol must be the broker's exact name, so look it up with search_symbols first; an unknown symbol fails the call with the terminal's reason. For just the live bid and ask of several symbols, get_quotes is lighter.

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": {
      "account_id": "<account_id>",
      "symbol": "<symbol>"
    },
    "name": "get_symbol_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesExact broker symbol name (see search_symbols).
account_idYesAn account_id from list_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine extra context beyond that: data is read live from the terminal, and an unknown symbol fails the call with the terminal's reason. It stops short of describing response shape beyond the field list, which is acceptable here.

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?

Front-loaded with the field enumeration, then the prerequisite, then the alternative — a sound ordering with no filler. The field list is long but each item is a distinct contract attribute an agent would want before calling, so it earns its space.

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?

With no output schema, the description compensates by enumerating what the call returns, and it covers the prerequisite lookup and the error behavior on bad input. Annotations carry the safety profile. Nothing an agent needs to invoke this correctly is missing.

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%, so both parameters are already documented, and the description's 'broker's exact name' largely restates the schema's 'Exact broker symbol name' plus the search_symbols pointer. It reinforces the exactness constraint and the failure consequence but adds little semantic detail the schema lacks. Baseline 3 applies.

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 ('Contract specification for one symbol at this account's broker') and enumerates the concrete fields returned (digits, contract size, tick size/value, volume limits, stops level, spread, swaps, commissions, sessions). It distinguishes itself from get_quotes by scoping to one symbol's full specification versus live bid/ask across several.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the prerequisite sibling ('symbol must be the broker's exact name, so look it up with search_symbols first'), states the failure mode for violating it, and routes the agent to get_quotes when only bid/ask is needed. Both when-to-use and an alternative are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FxSocket toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources