Skip to main content
Glama

Novarithm Agent Hub: trust and commerce checks

fx_chf_nok

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

This is very high. The description discloses crucial data characteristics: it is 'Official,' sourced from the 'European Central Bank fixing,' and explicitly states it is 'Deterministic, sourced, no estimate.' This provides essential context about the data's reliability and nature.

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?

While it is moderately dense, the information is highly valuable. It avoids fluff and front-loads key constraints (paid status, official nature) early on, making it efficient for an agent scanning options.

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?

The definition is complete for a zero-input tool. It specifies the data source, the methodology used for the rate (direct vs. cross), and the quality metrics of the result. Given the financial nature, this level of detail is essential for the agent to evaluate the appropriateness of the tool call.

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 no parameters. With 0 parameters and 100% schema coverage, the baseline score of 4 applies, and the description doesn't need to add semantic meaning to the arguments.

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 identifies the resource (CHF/NOK reference rate), the specific standard (European Central Bank fixing), and the components of the response. It is distinct from generic FX conversion tools and focuses precisely on providing an 'Official' rate.

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 definition implies usage for official or reference accounting needs by stressing its determinism and non-estimate status. However, it does not explicitly state when to use this tool versus other FX rate tools that might provide market-specific or real-time data.

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.