Skip to main content
Glama
Sign In
Stock Trade MCP Server

Stock Trade MCP Server

by JesusRS1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_forex_top_of_book

Retrieve real-time Forex top-of-book and last trade data for single or multiple ticker symbols.

Instructions

Fetches real-time Forex Top-of-Book/Last data for one or more ticker symbols.

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

Input Schema

NameRequiredDescriptionDefault
tickerNoForex ticker symbol (e.g., EURUSD)
tickersNoComma-separated Forex ticker symbols (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

There are no annotations, so the description must carry the behavioral burden. It does disclose that this is a read operation ('Fetches') and adds 'real-time' and 'Top-of-Book/Last', but it does not explain data limitations, authorization needs, or the meaning of 'Last' in this context.

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?

The description is a single, compact sentence that immediately states the function and scope. No unnecessary words or repetitions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple fetch tool, the description is adequate but incomplete: it lacks differentiation from the similar get_forex_prices tool and does not describe the return format or top-of-book terminology. The absence of an output schema means the description should clarify what data is returned, which it does not.

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%, giving a baseline of 3. The phrase 'one or more ticker symbols' adds a slight clarification that multiple symbols can be requested, but it does not explain the relationship between 'ticker' and 'tickers' nor which parameter is required.

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?

The description clearly states the action ('Fetches') and the resource ('real-time Forex Top-of-Book/Last data'), and notes support for one or more ticker symbols. This differentiates it from sibling tools like get_forex_prices and get_end_of_day_prices by specifying the real-time top-of-book nature.

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?

The description implies usage for real-time top-of-book data, but does not explicitly say when to choose this over get_forex_prices or other siblings. No exclusions or alternative recommendations are provided, leaving the selection based on the tool name and resource description.

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

Deploy Server

Other Tools