Skip to main content
Glama
Sign In
polygon-mcp

polygon-mcp

by atomcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

forex_get_quotes

Fetch NBBO quotes for a forex pair, providing bid/ask prices and timestamps to support market analysis and trading decisions.

Instructions

Get NBBO quotes for a forex pair.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
orderNo
symbolYes
timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Get NBBO quotes' without mentioning whether it returns current or historical data, how limit affects results, or any rate limits or pagination. This is a minimal disclosure of behavior.

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

Conciseness3/5

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

The description is a single concise sentence that is front-loaded with the verb. However, it is under-specified for a tool with 5 parameters and no schema descriptions, making it inappropriately sized for the complexity.

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

Completeness2/5

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

Given no annotations, no output schema, and 5 undocumented parameters, the one-sentence description is insufficient. It does not explain the return format, the meaning of parameters, or how this tool fits into the broader set of quote tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only hints at the symbol parameter via 'forex pair.' It provides no explanation for sort, limit, order, or timestamp, leaving all parameters undefined and failing to compensate for the schema's lack of descriptions.

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 states a specific action (Get) and resource (NBBO quotes for a forex pair), distinguishing it from related tools like forex_get_last_quote or forex_get_historic_ticks by the NBBO qualifier. It clearly identifies the asset class and the type of data returned.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as forex_get_last_quote, forex_get_historic_ticks, or stocks_get_quotes. The description provides no context about use cases, prerequisites, or exclusions.

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