Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

calc_currency_estimate

Read-onlyIdempotent

Estimate currency conversion using a rough rate; provide the amount, source currency, and target currency to calculate a practical estimate.

Instructions

Estimate currency conversion using a rough rate.

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": {
      "amount": "<amount>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "calc_currency_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds the useful caveat that the rate is rough, but it does not disclose rate source, freshness, rounding behavior, or what the estimate is based on.

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 definition is a single front-loaded sentence with no wasted words. It states the action and the key accuracy caveat immediately.

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?

For a simple three-parameter calculator, the description gives the core purpose and accuracy caveat, but with 0% schema coverage and no output schema it omits currency-code format and return-value expectations. It is minimally adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description does not explain parameter formats such as whether 'from' and 'to' are ISO currency codes, symbols, or names. It implies that amount, from, and to relate to currency conversion, but leaves the required syntax largely undocumented.

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 states a specific verb and resource: estimating currency conversion. The phrase 'rough rate' also signals that this is an approximate calculator rather than a precise FX converter, which helps distinguish it from sibling conversion tools, though no sibling is named.

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

Usage Guidelines3/5

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

The phrase 'rough rate' implies this tool is appropriate when an approximate currency estimate is acceptable, but it does not explicitly state when to use it instead of precise alternatives like forex_convert or exchangerate_convert. Usage is therefore implied rather than directed.

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