Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu

get_all_currencies

Retrieve all available currencies from Derive's market data to access comprehensive financial information for trading and analysis.

Instructions

Get all available currencies on Derive

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler method that makes the API request to the Derive API.
    getAllCurrencies(): Promise<unknown> {
      return this.post('public/get_all_currencies');
    }
  • src/tools.ts:22-26 (registration)
    Tool definition used by the MCP server to list available tools.
    {
      name: 'get_all_currencies',
      description: 'Get all available currencies on Derive',
      inputSchema: { type: 'object', properties: {} },
    },
  • Switch case logic in the MCP server's tool handler to invoke the client method for 'get_all_currencies'.
    case 'get_all_currencies':
      result = await client.getAllCurrencies();
      break;
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Get' implies read-only, the description discloses no information about rate limits, caching behavior, or the structure/format of the returned currency data.

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, six words. Front-loaded with no waste, appropriately sized for a zero-parameter utility function.

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 zero parameters and high (trivial) schema coverage, the description is minimally adequate. However, lacking an output schema, it should ideally describe what is returned (e.g., list of currency codes vs. detailed objects); this gap leaves it incomplete.

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. Per guidelines, baseline score is 4 when no parameters require semantic clarification beyond the empty schema.

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?

Clear verb 'Get' with resource 'currencies' and scope 'all on Derive'. The plural 'all' effectively distinguishes it from sibling tool 'get_currency' (singular), though it doesn't explicitly name that alternative.

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?

Provides no guidance on when to use this versus 'get_currency' for specific lookups, nor mentions if result sets are large or require pagination handling.

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/aadarshvelu/derive-mcp'

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