Skip to main content
Glama

quick_verify

Run a low-cost reality check on any claim to assess its plausibility and consistency. Receive a verdict, confidence score, and reasoning, with an abstention when uncertain.

Instructions

Cheap, fast reality-check on a CLAIM — the loopable default. PRICE: ~$0.02 per call (x402, USDC on Base mainnet). Ungrounded (no web search): a single calibrated Haiku judge over the claim's own plausibility/consistency — use it everywhere as the inexpensive first pass, then escalate the load-bearing ones to grounded_verify.

Returns: verdict (supported | unsupported | uncertain), an honest 0-1 confidence, reasoning,
and (when signing is enabled) a signed Ed25519 receipt you can later re-check for free with
verify_receipt. Abstains ('uncertain') rather than guess; never invents evidence.

Pricing is DISCLOSED and paid per use via x402 — Verity holds no key and never charges silently.
Optional affiliate_id tags the call for a future referral program (no split is paid until
public terms exist at veritylayer.dev); it does not change price or behavior.
(Independent fact-verification; maps to OWASP LLM/ASI guidance on grounding.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimYes
contextNo
affiliate_idNo
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: abstains rather than guesses, never invents evidence, pricing is disclosed and paid per use, Verity holds no key, and affiliate_id does not change behavior. This is exceptionally transparent for a tool with zero annotation support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the core purpose. Each sentence adds value—covering price, usage, outputs, limitations, and affiliate details—without any fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even without an output schema, the description explains the return values (verdict, confidence, reasoning, receipt) and includes pricing, limitations, and relationship to sibling tools. It is comprehensive for the tool's complexity.

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 thoroughly explains affiliate_id, and 'claim' is clear from the context, but the 'context' parameter is entirely unexplained. This leaves a meaningful gap in parameter semantics.

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 clearly states it is a 'Cheap, fast reality-check on a CLAIM' with a specific verb and resource. It explicitly contrasts with grounded_verify by calling itself 'ungrounded' and the 'inexpensive first pass,' distinguishing it from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage guidance: 'use it everywhere as the inexpensive first pass, then escalate the load-bearing ones to grounded_verify.' It also names the alternative tool (grounded_verify) and implies when not to use (for load-bearing claims).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/meloliva14/verity-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server