Skip to main content
Glama
Sign In
Financial Modeling Prep MCP Server

Financial Modeling Prep MCP Server

by imbenrabi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getForexBatchQuotes

Read-onlyIdempotent

Get real-time quotes for multiple forex pairs at once to track exchange rates and monitor price movements across global currency markets.

Instructions

Easily access real-time quotes for multiple forex pairs simultaneously with the Batch Forex Quotes API. Stay updated on global currency exchange rates and monitor price changes across different markets.

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

Input Schema

NameRequiredDescriptionDefault
shortNoOptional boolean to get short quotes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds only vague marketing language about staying updated and monitoring price changes, without disclosing data freshness, rate limits, return coverage, or whether it fetches all pairs or a specific set.

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

Conciseness2/5

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

The definition is two sentences, but the second sentence is pure promotional filler ('Stay updated... monitor price changes...') and the first leads with 'Easily access' rather than operational detail. It is not bloated in length, but it is not front-loaded with useful information.

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 tool with one optional parameter and no output schema, the description still fails to explain what the batch actually covers: which pairs are returned, how the caller specifies them, or how the 'short' flag changes output. The agent cannot confidently invoke it from this description alone.

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%, and the single optional 'short' boolean is fully documented in the schema. The description adds no parameter meaning beyond naming the batch concept, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it accesses real-time quotes for multiple forex pairs simultaneously, which gives a clear verb and resource. However, it does not clarify how the pairs are selected, what 'batch' means relative to siblings like getForexQuotes, or whether it covers all pairs or a supplied list.

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 getForexQuote, getForexShortQuote, getForexQuotes, or getBatchQuotes. The batch/multiple-pair framing implies a use case, but no alternatives or exclusions are stated.

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