Skip to main content
Glama
desk3
by desk3

get_exchange_rate

Retrieve current fiat currency exchange rates for cryptocurrency trading and financial analysis using real-time data.

Instructions

Get list of fiat currency exchange rates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function implementing the get_exchange_rate tool by fetching data from the Desk3 API endpoint.
    async def get_exchange_rate() -> dict[str, Any]:
        """
        Get list of fiat currency exchange rates.
        :return: Exchange rate data
        """
        url = 'https://mcp.desk3.io/v1/market/exchangeRate'
        try:
            return request_api('get', url)
        except Exception as e:
            raise RuntimeError(f"Failed to fetch exchange rate data: {e}")
  • Registration of the 'get_exchange_rate' tool in the MCP server's list_tools handler, including description and empty input schema.
    types.Tool(
        name="get_exchange_rate",
        description="Get list of fiat currency exchange rates",
        inputSchema={
            "type": "object",
            "properties": {},
            "required": [],
        },
    ),
  • Dispatch handler in the MCP @server.call_tool that executes get_exchange_rate and returns the result as formatted JSON text content.
    case "get_exchange_rate":
        try:
            data = await get_exchange_rate()
            return [
                types.TextContent(
                    type="text",
                    text=json.dumps(data, indent=2),
                )
            ]
        except Exception as e:
            raise RuntimeError(f"Failed to fetch exchange rate data: {e}")
  • JSON Schema definition for the tool's input parameters (none required).
    inputSchema={
        "type": "object",
        "properties": {},
        "required": [],
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does without mentioning any behavioral traits such as data freshness, rate limits, authentication needs, or response format. This is inadequate for a tool with no annotation coverage.

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 description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool's low complexity (0 parameters, no annotations, no output schema), the description is minimally adequate but lacks depth. It does not explain return values or behavioral context, which could be important for financial data tools, leaving gaps in completeness.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description does not add parameter details, but since there are no parameters, a baseline of 4 is appropriate as no additional semantic information is needed.

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 clearly states the action ('Get') and resource ('list of fiat currency exchange rates'), providing a specific purpose. However, it does not differentiate from sibling tools like 'get_token_price' or 'get_mini_24hr', which might also involve financial data, so it lacks sibling distinction.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_token_price' and 'get_fear_greed_index' that might overlap in financial contexts, there is no explicit or implied context for usage, leaving the agent without direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/desk3/cryptocurrency-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server