Skip to main content
Glama
AllRatesToday MCP Server

AllRatesToday MCP Server

Request a trial API key

request_trial_key

Issue a 7-day AllRatesToday API key with 100 lifetime calls when a rates tool requires a key, so users can get real-time currency rates or history without an account or email.

Instructions

Self-issue an AllRatesToday API key with 100 lifetime calls, valid 7 days, with no account and no email. Use it when another tool answered "needs an API key" and the user wants real-time rates or history right now. The key is adopted by this server for the rest of the session and returned once — tell the user to put it in the MCP config as ALLRATES_API_KEY to keep it. Capped at 3 keys per IP per day. For a lasting key, register at https://allratestoday.com/register (free) or see https://allratestoday.com/pricing.

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

Input Schema

NameRequiredDescriptionDefault
agentNoOptional: the agent or product requesting the key.
purposeNoOptional: one line on what the rates are for.

Output Schema

NameRequiredDescriptionDefault
keyNo
noteYes
callsNo
adoptedYesTrue when this server switched to the new key
expires_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.9

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare a non-read-only, open-world, non-idempotent operation. The description goes well beyond that: the key is adopted server-side for the remainder of the session, the secret is returned exactly once and must be persisted to the MCP config as ALLRATES_API_KEY, and issuance is capped at 3 keys per IP per day. Those are the exact facts an agent needs before invoking a mutating, irreversible-return tool.

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?

Front-loaded with what the tool yields and its limits, then the trigger condition, then the post-call obligations, then the rate cap and escape hatch. Every sentence contributes a distinct operational fact; nothing repeats the name or title.

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

Completeness5/5

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

Output schema exists, so return shape needn't be narrated. Combined with the validity window, call cap, session-adoption behavior, one-time secret disclosure, and the persistence instruction, an agent has everything needed to call it and to advise the user correctly.

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?

Both parameters are optional and fully documented in the schema (100% description coverage), so the schema carries the semantics. The description adds nothing about the agent or purpose fields, which is acceptable under the high-coverage baseline but leaves no extra meaning.

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?

States a specific verb and resource ("Self-issue an AllRatesToday API key") and pins down the exact scope: 100 lifetime calls, 7-day validity, no account or email. This is immediately distinguishable from the sibling lookup tools, which consume keys rather than mint them.

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

Usage Guidelines5/5

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

Gives an explicit trigger condition ("when another tool answered 'needs an API key'") plus the user intent that justifies it, and names the alternative for the persistent case (register at the free registration URL or see pricing). When-to-use and when-not-to-use are both covered.

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