Skip to main content
Glama
Sign In
Travel Agent MCP

Travel Agent MCP

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

convert_currency

Read-onlyIdempotent

Convert any amount between currencies with live reference rates. Get quick spending context before diving into trip planning.

Instructions

FREE live reference-rate currency conversion from the ForgeMesh travel-agent backend. Use when a traveler or agent needs quick spending context before deciding whether to ask for richer x402 trip guidance. Read-only, no account setup, no payment, and not a transaction quote.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "convert_currency"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget ISO 4217 currency code, such as EUR.
dateNoOptional reference date in YYYY-MM-DD format when supported by the backend.
fromYesSource ISO 4217 currency code, such as USD.
amountNoAmount to convert. Default: 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds that it is free, no account setup, no payment, and not a transaction quote, enriching transparency without contradictions.

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?

Two sentences, front-loaded with key purpose and usage context, no extraneous words.

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?

Given rich annotations and fully described parameters, the description provides all necessary context: it is a free, read-only reference conversion, not a quote. No output schema needed.

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?

Schema description coverage is 100%, so the description does not need to add parameter details. It adds minimal semantic value beyond stating 'live reference-rate' but does not elaborate on parameters.

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?

The description clearly states it performs currency conversion using live reference rates from ForgeMesh. Among siblings, no other tool does currency conversion, so it is well-distinguished.

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?

Explicitly says when to use (quick spending context before richer guidance) and what not to use for (not a transaction quote), providing clear guidance.

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