Skip to main content
Glama
Sign In

Novarithm Agent Hub: trust and commerce checks

by com.novarithm.www
OverviewDiscussionsAdmin

property_gb

[PAID $0.02 USDC/call, x402, eip155:8453] Average price actually paid and number of sales per full postcode, from HM Land Registry price paid data: pass a postcode prefix (SW1A) or a full postcode. Signed, source cited, no estimate involved.

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": {
      "postcode": "<postcode>"
    },
    "name": "property_gb"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesFull postcode or prefix, e.g. SW1A or SW1A 1AA

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 on the dimensions that matter most: it discloses that the call is paid ($0.02 USDC, x402, eip155:8453) up front, and that responses are signed, source-cited, and non-estimated. It omits operational traits like latency, failure modes, or what happens when a prefix matches no sales.

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?

Essentially one sentence with a bracketed payment/scheme tag up front. The cost and protocol disclosure is front-loaded where an agent will see it, and nothing is filler, though the bracket tag is dense and slightly disrupts reading flow.

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 one-parameter read tool with no output schema and no annotations, the description covers the essentials: what is returned (average price + sales count), the data source, the payment requirement, and trust properties. Only the response shape specifics and edge-case behavior remain unstated.

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?

Schema coverage is 100% on the single parameter, so baseline is 4. The description reinforces the two accepted forms (prefix or full postcode) but adds no normalization rules, casing/space handling, or notes on how prefix-level aggregation differs from full-postcode results.

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: average price actually paid and sale counts per postcode, sourced from HM Land Registry price paid data. That is concrete enough to separate it from generic lookup siblings, though it never explicitly contrasts with uk_postcode, which is the closest potential overlap.

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 context is only implied: it is clearly a UK property-price aggregate lookup. The description says a prefix (SW1A) or a full postcode may be passed, but gives no guidance on which granularity to choose for which question, no eligibility constraints, and no named alternative tool.

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