Retrieve real-time quotes and price changes for multiple forex currency pairs in a single batch request, enabling quick comparison and monitoring of forex market movements.
Retrieve real-time quotes for multiple forex currency pairs with the FMP Batch Forex Quote API. Get real-time price changes and updates for a variety of forex pairs in a single request.
| Name | Required | Description | Default |
|---|---|---|---|
| short | No | Whether to use short format |
Changes observed during successful MCP inspections.
v2.9.0Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish that this is a read-only, idempotent, open-world operation. The description adds useful context that the data is real-time and batch-oriented, but it does not disclose rate limits, authentication needs, return format, or how pairs are selected.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose and uses only two sentences. There is minor redundancy, since 'real-time' is repeated and 'a variety of forex pairs' restates 'multiple forex currency pairs', but it remains efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, single-parameter tool with annotations covering safety, the description is mostly sufficient. However, without an output schema, it does not explain the returned fields or whether the batch covers all pairs or a caller-specified set, which leaves meaningful ambiguity for a batch forex quote tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for its single optional parameter, 'short', so the schema already carries the parameter documentation. The description does not add any meaning about what 'short format' changes or when to set it, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: retrieve real-time quotes for multiple forex currency pairs via a batch API. It clearly conveys the batch scope, but it does not distinguish this tool from the similarly named sibling getForexBatchQuotes or from the singular getForexQuote.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'multiple forex currency pairs' and 'in a single request' implies this tool is for batch retrieval rather than single-pair lookup. However, it gives no explicit when-to-use guidance, no exclusions, and does not name alternatives such as getForexQuote or getForexBatchQuotes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.