Skip to main content
Glama
Sign In

Finance Database

by io.github.JerBouma
OverviewDiscussionsAdmin

cryptos

Read-onlyIdempotent

List cryptocurrency pairs matching a cryptocurrency (e.g. 'ETH') and/or the currency it is quoted in (e.g. 'USD' or 'BTC'), or matching a free-text query on symbol or name. Every filter accepts one value or several comma-separated values.

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

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).
currencyNoTrading currency as an ISO code, e.g. 'USD' or 'EUR'. Several values: comma-separated (e.g. 'A, B') or a list. Case-insensitive.
show_columnsNoColumns to return, comma-separated. Default: symbol, name, cryptocurrency, currency, exchange. Available: symbol, name, cryptocurrency, currency, summary, exchange, website.
cryptocurrencyNoCryptocurrency code, e.g. 'ETH', 'ADA' or 'XRP'. 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 declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and side-effect questions are answered structurally. The description adds the useful combination semantics ('and/or') between filters, but says nothing about result ordering, paging behavior, or truncation beyond what the schema already states.

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?

Two sentences, front-loaded with the resource and the filtering modes, with no filler. The trailing sentence about comma-separated values largely duplicates the schema's own 'Several values: comma-separated' wording, which is the only real redundancy.

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?

With 0 required params, full schema coverage, annotations covering the safety profile, and show_columns enumerating the returnable fields, little is left for the description to carry. It adequately covers what the tool is and how filters combine; return-shape detail is handled by the schema.

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%, with each parameter (limit, query, offset, currency, cryptocurrency, show_columns, include_summary) documented in detail, so the baseline is 3. The description contributes the cross-parameter combination logic but otherwise restates the multi-value convention already present in every schema field.

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?

States a specific verb ('List') and resource ('cryptocurrency pairs') plus the three ways to filter them (by cryptocurrency, by quote currency, or by free-text query). The resource is clearly distinct from the sibling set (currencies, equities, etfs, indices), though no sibling is named explicitly.

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?

The 'and/or' phrasing implies the filters can be combined or used singly, which gives an agent a usable mental model. However, there is no explicit when-to-use versus when-not guidance and no routing to alternatives such as search_instruments for broader lookups.

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