Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

quote_cost_normalize

[PAID $0.008 USDC/call, x402, eip155:8453] Normalize exact decimal quote amounts using supplied currency rates. Up to 1000 total line items. Missing shipping, tax or other costs stay unknown. Rank only complete quotes for identical supplied item-ID/quantity baskets; no rate verification, fiscal advice or order. EOA EIP-712 payments only; ERC-1271/6492 unsupported. MCP body max 64 KiB. Experimental price; input facts are not authenticated.

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": {
      "base_currency": "<base_currency>",
      "quotes": "<quotes>"
    },
    "name": "quote_cost_normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratesNo
quotesYes
base_currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: discloses paid x402 pricing ($0.008 USDC, eip155:8453), EOA EIP-712-only auth with ERC-1271/6492 unsupported, 1000 line-item cap, 64 KiB body limit, and that missing shipping/tax/other costs remain unknown. These are precisely the traits structured fields do not convey.

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?

Payment and purpose are front-loaded, then constraints in descending importance. Dense but every sentence carries information; the bracketed price preamble and trailing 'experimental price' notice are slightly redundant but not wasteful.

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?

Given no annotations, no output schema, and undocumented parameters, the description covers payment model, auth constraints, limits, and edge-case treatment well. It is weaker on what the normalized/ranked output actually looks like, which matters more since there is no output schema.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate; it adds that rates are 'supplied' (no external lookup) and that quotes may have unknown shipping/tax/other costs. However base_currency, rate_to_base, and the quotes/items nesting remain only inferable from the schema, leaving real gaps.

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?

States a specific verb+resource: 'Normalize exact decimal quote amounts using supplied currency rates', plus the ranking behavior for identical item-ID/quantity baskets. An agent can grasp what it does, though it never names fx_convert/fx_latest or explains how it differs from those siblings.

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?

Provides scope exclusions ('no rate verification, fiscal advice or order') and a usage condition ('Rank only complete quotes for identical supplied item-ID/quantity baskets'), but never states when to prefer this over the sibling fx_convert/fx_latest tools or what prerequisites to satisfy first.

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