Skip to main content
Glama
Sign In
polygon-mcp

polygon-mcp

by atomcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

forex_get_last_quote

Retrieve the current market quote for any forex pair by specifying its base and quote symbols.

Instructions

Get the last quote 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": {
      "from_symbol": "<from_symbol>",
      "to_symbol": "<to_symbol>"
    },
    "name": "forex_get_last_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_symbolYes
from_symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states what the tool does at a high level, without explaining the meaning of 'last quote' (e.g., bid/ask), data freshness, or any side effects (which are likely none). No additional behavioral context is provided.

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, clear, front-loaded sentence with no filler words. Every word contributes to the core purpose, making it highly concise and easy to parse.

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?

For a simple two-parameter tool, the description is extremely sparse. There is no output schema, so the description should clarify what a 'last quote' contains (e.g., price, bid/ask, timestamp) but does not. It also lacks any contextual hints about data source, delay, or real-time behavior, which would be expected given sibling tools differentiate these aspects.

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

Parameters2/5

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

The schema has two parameters with zero descriptions (coverage 0%). The description implies that the two symbols form a forex pair, but it does not specify which is the base or quote currency, nor provide any examples (e.g., 'from_symbol=EUR, to_symbol=USD'). It adds minimal meaning beyond the parameter names.

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 tool's function: 'Get the last quote for a forex pair.' It uses a specific verb ('Get'), a specific resource ('last quote'), and clearly distinguishes from sibling tools by specifying 'forex pair' and 'last quote' rather than historical or aggregated data.

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 compared to alternatives like forex_get_quotes, forex_get_historic_ticks, or real-time conversion. The description does not mention any exclusions or prerequisites.

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