verified-feed

verify_record

Run a contradiction-verified, signed verification on ONE record of a data owner's feed. Attaches a verification STATUS (VERIFIED / CONTRADICTED / EXCLUSION_HIT / UNVERIFIABLE), an AS-OF date, source links, and a tamper-evident hash-chain receipt — by re-checking the record's subject against the live contradiction-engine (SEC 10-K vs USAspending) and, for named entities, the live exclude-feed. A dated evidence statement, never a guarantee.

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": {
      "record": "<record>"
    },
    "name": "verify_record"
  }
}

Input Schema

Name	Required	Description	Default
`feed`	No	Feed slug the record belongs to (used for SLA + receipt scoping).
`record`	Yes	{ id, subject:{ticker?, name?}, claim? }

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 22, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the verification process, live checks, attached information (status, as-of date, sources, receipt), and the caveat that it is a dated evidence statement, never a guarantee.

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?

The description is relatively concise, packing significant detail into two sentences. It is front-loaded with the primary action and clearly structured, though the first sentence is long and could be broken for readability.

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?

Given the tool's complexity (contradiction engine, multiple statuses, hash-chain receipt), the description covers all essential aspects: inputs, process, outputs, and limitations. No output schema exists, so the description adequately replaces it.

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?

Input schema coverage is 100%, so baseline is 3. The description adds context about the verification process and outputs, but does not provide additional semantic meaning for each parameter beyond what the schema already defines.

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 the tool runs a contradiction-verified, signed verification on one record of a data owner's feed, listing specific statuses and outputs. It distinguishes itself from siblings like verify_subject by focusing on a single record.

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?

The description implies usage for verifying a single record and checking against live engines, but does not explicitly provide when to use this tool versus alternatives like verify_subject or verify_receipt.

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

All verified-feed tools Inspect

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

Need Help?