Skip to main content
Glama

ExchangeRebel — pay-per-call APIs for AI agents (x402 on Solana)

provenance_criteria

The published criteria for the Memory Provenance Audit service (memory-provenance-audit/v1): the eight provenance checks C1-C8 plus C9 chain integrity, the input format adapters (Mem0, Zep/Graphiti, generic JSONL, hash-only), the verdict-line rule, the custody block and retention terms, and the pinned public test corpus identity (corpus, harness and the C13 self-grade fixture are published at https://exchangerebel.com/provenance/). Read these before paying - every verdict is reproducible from them. - no payment required: call directly without payment (no x402 challenge; this tool is free). HTTP equivalent: GET https://exchangerebel.com/toll/provenance/criteria.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "provenance_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningful work: it discloses that the tool is free and issues no x402 challenge, that results are reproducible and therefore auditable, and that retention and custody terms are part of the returned content. It does not describe the shape of the returned document (plain text vs. structured), which leaves a modest gap for a no-argument tool.

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 content is densely packed into a single long sentence with a trailing free-access note and endpoint, so the most decision-relevant point (this is the spec you must read before paying) is front-loaded. The mid-sentence enumeration of adapters and clauses is heavy but each item is substantive rather than 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?

For a zero-parameter, no-output-schema specification tool, the description is close to complete: it lists the document's contents, states the cost model, and points to the public corpus. The only omission is any indication of the retrieval format or size of the returned criteria document.

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?

Parameter count is zero, so there is nothing to disambiguate and the baseline of 4 applies. The description adds no parameter detail because none exists, which is appropriate.

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 names a specific resource (the published criteria for the Memory Provenance Audit service, memory-provenance-audit/v1) and enumerates exactly what it contains: checks C1-C8 plus C9 chain integrity, the input format adapters, the verdict-line rule, the custody block and retention terms, and the pinned corpus identity. That distinguishes it clearly from the sibling provenance_receipt, which is the action tool rather than the specification.

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?

It gives a clear use instruction: 'Read these before paying - every verdict is reproducible from them,' which establishes sequencing relative to the paid verdict tool. It also states the call needs no payment and provides an HTTP equivalent. It stops short of explicitly naming provenance_receipt as the follow-up tool, so the when/when-not routing is implied rather than stated.

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.

Resources