Skip to main content
Glama
Sign In

Finance Database

by io.github.JerBouma
OverviewDiscussionsAdmin

currencies

Read-onlyIdempotent

List currency pairs matching a base currency and/or quote currency (ISO codes, comma-separated for several), or matching a free-text query on symbol or name (e.g. query='EURUSD').

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 25, maximum 200).
queryNoOptional free-text search on symbol and name (case-insensitive substring, e.g. 'apple' or 'AAPL'); an ISIN also matches where available. Best matches come first.
offsetNoRows to skip, for paging (see the `_notes` hint in the response).
show_columnsNoColumns to return, comma-separated. Default: symbol, name, base_currency, quote_currency, exchange. Available: symbol, name, base_currency, quote_currency, summary, exchange.
base_currencyNoBase currency of the pair as an ISO code, e.g. 'EUR' in EURUSD. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
quote_currencyNoQuote currency of the pair as an ISO code, e.g. 'USD' in EURUSD. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
include_summaryNoAdd the business/fund description (truncated to 300 characters). Off by default to keep responses small.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation, so the description only needs to add context beyond that. It adds matching semantics for the filters, but does not describe result ordering for base/quote filtering, pagination behavior, or how multiple filter modes combine; those are left to the schema and response notes.

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

Conciseness4/5

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

The definition is a single dense sentence that is front-loaded with the operation and resource, then moves into filter semantics. It is efficient and has no wasted framing, though the two matching modes packed into one sentence make it slightly harder to scan.

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

Completeness4/5

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

For a simple read-only list tool with seven optional parameters and full schema coverage, the description provides enough context to select and invoke it correctly. It omits paging and output-shaping details, but those are fully documented in the schema and there is no output schema requiring explanation.

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%, so the baseline is 3. The description reinforces the meaning of base_currency, quote_currency, and query with ISO-code and free-text examples, but this largely repeats what the schema already documents and does not add syntax or format details beyond it.

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

Purpose4/5

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

The description uses a specific verb and resource, 'List currency pairs', and defines the two matching modes: ISO base/quote filters and free-text symbol/name search. It clearly differentiates the tool's scope from non-currency siblings like cryptos, equities, and etfs by naming currency pairs, though it does not explicitly reference those alternatives.

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?

It explains how to use the filters, including comma-separated ISO codes and the example query='EURUSD', which implies the intended use case. However, it gives no explicit when-to-use guidance against siblings such as search_instruments or search_categories, and no exclusions or prerequisites.

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

All Finance Database toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources