Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_myr_dkk

[PAID $0.002 USDC/call, x402, eip155:8453] Official MYR/DKK reference rate: latest European Central Bank fixing (or the official peg when DKK is pegged), with the rate date, the method (direct, cross via EUR or peg-derived) and the source attribution. Deterministic, sourced, no estimate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description does substantial work by disclosing the exact $0.002 USDC per-call charge, x402 payment mechanism, eip155:8453 network, ECB source, possible calculation methods, and deterministic no-estimate behavior. It also previews the rate date and attribution, although publication timing, freshness expectations, and failure behavior remain unstated.

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 compactly covers cost, network, scope, source, methodology, returned metadata, and result quality without procedural filler. The payment prefix and long opening sentence make it somewhat dense, and "sourced" slightly repeats the promise of source attribution.

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?

For a zero-argument lookup without an output schema, the description adequately explains the conceptual result: a rate accompanied by its date, method, and source attribution, plus the invocation cost. It would be more complete with explicit quote orientation, such as DKK per MYR, the publication or update cadence, and clearer differentiation from conversion and historical-rate siblings.

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?

There are no input parameters, so the baseline of 4 applies and no parameter documentation is required. The fixed MYR/DKK scope and "latest" wording reinforce that callers do not select currencies, an amount, or a historical date.

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 identifies a specific resource and scope: the latest official MYR/DKK reference rate, with a sourced fixing rather than an estimate. It does not explicitly contrast nearby siblings such as fx_convert, fx_latest, or fx_dkk_myr, so sibling differentiation remains implicit.

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

Usage Guidelines4/5

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

The terms "latest," "Official," and "no estimate" establish a clear use case: obtaining the current official reference rate with provenance. There is no explicit routing for amount conversion, historical rates, or the reverse currency pair, which would require naming alternatives such as fx_convert, fx_timeseries, or fx_dkk_myr.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.