Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

trust_trio

[PAID $0.010 USDC/call, x402, eip155:8453] Trust Trio: A2A agent card + MCP server probe + x402 payment-offer check of one AI agent in a single call (no payment made to it). Returns trusted/partial/untrusted, a trust score and every issue.

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": {
      "url": "<url>"
    },
    "name": "trust_trio"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAgent base URL or domain (A2A card looked up at the domain root)
mcp_urlNoMCP endpoint (default: <url>/mcp)
x402_urlNoPaid endpoint to check for a 402 offer (default: url)
x402_methodNoHTTP method for the x402 check

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses metered cost ($0.010 USDC/call via x402 on eip155:8453), a key safety property (no payment is made to the target), and the output shape (trusted/partial/untrusted, trust score, every issue). It omits failure/timeout behavior and what happens when a sub-check is unreachable.

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?

Price and mechanism are front-loaded in a bracket, followed by a single dense sentence covering scope, side-effect caveat and return values. No redundant sentences, though the sentence is packed tightly enough that parsing takes a second reading.

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?

No output schema or annotations exist, so the description must supply the verdict vocabulary, the score, and the no-payment guarantee — all present, plus pricing for cost-aware agents. Remaining gaps are edge-case behavior (partial failures, timeouts) that an agent could reasonably want before calling.

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 coverage is 100%, so defaults and the x402_method enum are already documented. The description only adds the framing 'of one AI agent', which implies all inputs refer to a single target, but adds no format or constraint detail beyond the schema.

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?

States exactly what it does: a combined A2A card + MCP probe + x402 offer check of one AI agent in a single call, with the verdict it returns. The three named components make clear it subsumes the separate a2a_card_check, mcp_probe and x402_probe siblings rather than duplicating them.

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?

'In a single call' implies it is the one-shot alternative to running the three individual probes, and '(no payment made to it)' clarifies it will not settle a payment, distinguishing it from verify_usdc_payment. No explicit when-not conditions or named alternatives are given, keeping it short of a 5.

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