Skip to main content
Glama
Sign In
CSPR[dot]trade MCP

CSPR[dot]trade MCP

by make-software
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_currencies

Retrieve a list of supported fiat currencies for displaying cryptocurrency prices on the CSPR.trade decentralized exchange.

Instructions

List supported fiat currencies for price display

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. 'List' implies read-only behavior, but description omits return format details, pagination behavior, or whether results are cached/static.

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?

Single sentence, front-loaded with the action verb. Every word serves purpose: verb (List), resource (supported fiat currencies), context (for price display). No waste.

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?

Appropriate for a zero-parameter list tool. While no output schema exists, the description sufficiently communicates the tool's scope for its complexity level. Minor gap: doesn't describe return value structure (e.g., array of currency codes).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters present, which per rules sets a baseline of 4. Description correctly avoids inventing parameters that don't exist in the schema.

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?

Excellent clarity: 'List' is a specific verb, 'supported fiat currencies' defines the resource precisely, and 'for price display' clarifies the contextual purpose. It clearly distinguishes from sibling get_tokens (crypto) by specifying 'fiat'.

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?

Provides implied usage context ('for price display') indicating when to use it, but lacks explicit guidance on when NOT to use it or alternatives (e.g., no mention of get_tokens for crypto assets).

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