Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

fx_cad_sgd

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the most decision-critical traits: paid at $0.002 USDC per call over x402 on eip155:8453, deterministic, sourced, no estimation, and it names the fallback path (peg-derived) when SGD is pegged. It stops short of stating freshness cadence, response shape, or failure behavior for non-fixing days.

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 tightly packed sentences with the pricing tag front-loaded, then purpose, then return contents. Every clause carries information, though the parenthetical enumerating methods (direct, cross via EUR, peg-derived) is dense enough that it verges on schema-level detail.

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-parameter tool with no output schema, the definition covers source, method, determinism, cost, and the main returned fields (rate date, method, attribution). What is missing is the concrete response shape—field names, rate precision, and base/quote orientation—which an agent would need to parse the result reliably.

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; the baseline of 4 applies. The description correctly implies the pair is fixed by the tool identity rather than passed as an argument.

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 names a specific resource (CAD/SGD reference rate) and its authoritative source (latest ECB fixing, or the official peg for SGD), which is exactly the granularity needed to distinguish this tool from the hundreds of sibling fx_* pair tools. An agent can tell instantly that this returns the CAD-to-SGD rate and nothing else.

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 infers it should call this when it needs a CAD/SGD rate. There is no explicit routing to alternatives such as fx_convert (arbitrary conversion), fx_latest, or fx_timeseries, and no stated conditions for when the official ECB reference is preferred over a market rate.

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

All Novarithm Agent Hub: trust and commerce checks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources