Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_dkk_myr

[PAID $0.002 USDC/call, x402, eip155:8453] Official DKK/MYR reference rate: latest European Central Bank fixing (or the official peg when MYR 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_dkk_myr"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the paid access model and price ('[PAID $0.002 USDC/call, x402, eip155:8453]'), the provenance (ECB fixing with source attribution), the fallback behavior (official peg when MYR is pegged), and the response fields (rate, rate date, derivation method). It does not say what happens when no rate is available, whether results are cached, or how stale a fixing can be before it is replaced.

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?

Two sentences, no filler, and the payload (pair, source, derivation, return fields) is front-loaded after the required payment tag. The closing 'Deterministic, sourced, no estimate' is mild promotional padding, and the price bracket slightly delays the purpose statement.

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 trivial zero-parameter lookup with no annotations and no output schema, the description covers essentially everything an agent needs: cost, source, fallback semantics, and the values returned. Only the failure/no-rate path and the exact response shape are unaddressed, which is minor given there is nothing to configure.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly keeps the pair fixed rather than implying any selectable currency arguments.

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 names the exact resource: 'Official DKK/MYR reference rate: latest European Central Bank fixing', which pins down both the currency pair and the data source, so an agent can tell it apart from the hundreds of other fx_<a>_<b> siblings by name alone. It stops short of distinguishing itself from the aggregate siblings such as fx_latest, fx_convert or fx_timeseries, which is what would be needed for a 5.

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?

Usage is only implied: an agent can infer 'call this when you need the DKK/MYR rate'. There is no explicit when-to-use, when-not-to-use, or pointer to the alternative tools (fx_convert for conversion, fx_timeseries for history, fx_latest for a full table), so the routing decision is left to inference.

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.