Skip to main content
Glama

Verified Brief Payment Quote

verified_brief_quote
Read-onlyIdempotent

Returns the payment instructions (the unpaid HTTP 402) for the $0.25 verified brief; this tool never runs the brief or pays. To get the brief, pay the 402 over HTTP with x402 v2 (USDC or EURC on Base only) at GET https://horizonpulse.dev/api/research/report/brief?q=... Verified brief, three question types only: Base or Ethereum gas (on-chain read), USDC supply on Ethereum and Base (on-chain totalSupply), or an x402 spec fact. For USDC on Base: charged only if at least 2 claims are confirmed in two sources as defined by the contract (two independent publishers, two independent nodes, or two separate specification documents); otherwise a 422, unpaid. Contract: https://horizonpulse.dev/contracts/brief-verified. Terms: https://horizonpulse.dev/premium-terms.

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": {
      "q": "<q>"
    },
    "name": "verified_brief_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesQuestion about Base or Ethereum gas, USDC supply on Ethereum and Base, or an x402 spec fact. No personal data.
typeNoOptional: skip phrase matching and use this question type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: the exact price, that nothing is charged unless at least 2 claims are confirmed in two independent sources per the contract, that failure returns a 422 unpaid, and that payment is restricted to USDC/EURC on Base. It even links the contract and terms so charging rules can be verified.

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?

Front-loaded with the single most decisive fact — it returns a 402 and does not execute anything — with payment mechanics and pricing following in logical order. It is dense and URL-heavy, and the 'three question types' phrasing is compressed to the point of ambiguity, but no sentence is filler.

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?

With no output schema, the description carries the return-value burden and does so well by naming the payload as an unpaid HTTP 402 plus the endpoint to pay it at. Pricing, chain, currency, and failure semantics are all covered; the only gap is the mild three-vs-four question-type inconsistency relative to the enum.

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%, so the baseline would be 3; the description earns a bump by constraining what `q` may contain (gas, USDC supply, or an x402 spec fact, no personal data) and explaining that `type` skips phrase matching. Minor friction: it says 'three question types only' while the enum exposes four values, which mildly muddies the mapping.

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 a specific verb and object — returns the unpaid HTTP 402 payment instructions for the $0.25 verified brief — and immediately delimits scope with 'this tool never runs the brief or pays.' That negative clause sharply separates it from sibling '*_quote' tools and from any tool that would execute the underlying request.

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?

Gives clear operational context: call this to obtain the 402, then pay it over HTTP with x402 v2 (USDC or EURC on Base only) at the stated endpoint. It also scopes the acceptable question types. What it lacks is an explicit routing statement naming alternatives (e.g., which sibling quote tool to use for non-brief research), leaving the agent to infer the boundary.

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.