Skip to main content
Glama

StackerScan

Supported currency catalog

list_supported_currencies
Read-only

The live list of codes every currency/base parameter accepts — ISO 4217 fiat plus the metal codes.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoCase-insensitive substring match against code or name.
cursorNoOpaque continuation token returned by the same tool with exactly the same filters.

Output Schema

NameRequiredDescriptionDefault
queryYes
currenciesYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / currencies / items / title
      Added value: +"Currency"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description adds key domain knowledge regarding data coverage—that it includes both ISO 4217 fiat codes and metal codes. This scope information is a crucial behavioral trait that goes beyond the standard safety assurances provided by the annotations.

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 definition is extremely concise, using a single sentence to deliver maximum information regarding the tool's purpose, scope (fiat and metal), and audience (parameter acceptance). There is zero wasted wording or structure that could be improved.

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?

Given the schema handles the mechanics of pagination (limit/cursor) and the description handles the scope of the data, the definition is highly complete. It fully informs the user about the nature and quality of the information returned, fulfilling its role well.

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?

Since schema description coverage is 67%, the description adds context by defining *what* the resulting list represents rather than explaining the parameters. It serves its purpose by framing the tool's utility (what data it validates) but doesn't elaborate on the specific mechanics of the limit, query, or cursor.

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 defines the tool's function: providing a list of supported codes. It explicitly mentions ISO 4217 fiat and metal codes, which defines the resource scope and successfully distinguishes itself from sibling price-fetching tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides strong usage guidance by stating the list is for codes accepted by `currency`/`base` parameters. While it doesn't explicitly name a 'not' use case, the highly specific functional context implies its correct place in the workflow, suggesting it is used prior to any price query.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources