Skip to main content
Glama
Sign In
API Hub MCP — 337+ Tools

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

currency_cross

Retrieve cross-currency exchange rates for current or historical dates. Convert amounts between currencies with source, target, and optional date.

Instructions

Get cross-currency exchange rates with optional historical date.

Parameters:
    from_currency — Source currency code (default: 'USD').
    to_currency — Target currency code (default: 'EUR').
    amount — Amount to convert (default: 1).
    date — Historical date (ISO format, optional). Leave empty for current rate.

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

Input Schema

NameRequiredDescriptionDefault
from_currencyNoUSD
to_currencyNoEUR
amountNo
dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the tool fetches exchange rates, without mentioning rate limits, authentication requirements, side effects, or response behavior. This is minimal transparency for a data retrieval tool.

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?

The description is short with a one-sentence summary followed by a parameter bullet list. It is front-loaded and efficient, though the bullet list repeats some schema defaults. Overall, every sentence contributes to understanding.

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?

The tool has four optional parameters and an output schema. The description covers parameter meaning adequately, and the purpose sentence implies the output (exchange rates). With no annotations, it could mention output structure or limitations, but the presence of an output schema reduces the need. Complete for basic usage.

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?

Schema coverage is 0%, so the description must compensate. It provides brief explanations for each parameter (source/target currency, amount, date with default values). While helpful, it lacks detail like valid currency codes, date format specifics, or amount constraints. This adds meaning beyond the schema but could be richer.

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?

Description clearly states 'Get cross-currency exchange rates with optional historical date,' specifying a distinct verb, resource, and optional scope. This distinguishes it from siblings like 'convert_currency' and 'list_currencies' by focusing on rate retrieval with a historical feature.

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?

No guidance on when to use this tool versus alternatives such as 'convert_currency' or 'list_currencies.' The description lacks context for choosing between tools, leaving the agent without decision support.

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