Skip to main content
Glama

TWZRD Agent Intelligence

submit_contribution_claims

Read-onlyIdempotent
PoECX bridge: report settlements from your OWN rails (not TWZRD's paid
routes) for cross-check against TWZRD's independently-ingested x402
corpus, by on-chain signature.

A claim whose tx_signature, payer/merchant, and amount all match what
TWZRD's own ingest independently observed is materially stronger evidence
than either a bare self-report or the anonymous corpus alone — the
signature is real and on-chain, and a mismatch can't be forged to pass.
Unmatched claims are returned too, with a reason, never silently dropped.

This is a preview, not an unlock: `claimable` is always false. It exists
to let a real counterparty with its own settlement volume start feeding
PoECX before any on-chain payout path exists — see the PoECX plan.

Capped at 25 claims per call (discovery convenience, not bulk export);
extras are dropped, never silently ignored — see `capped`/`claims_requested`.
Within that cap, only the first claim per (chain, tx_signature,
transfer_index) is checked. Omitted transfer_index is the first leg
(dedup key 0). Later copies of the same leg appear in `unverified`
with reason_code `duplicate_claim` and `duplicate_of` pointing to the
zero-based first input index. Two legs of one tx count twice. This
deduplicates one preview report, not claims across separate calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimsYesSelf-reported settlements to cross-check. Each item: {"tx_signature": str, "chain": "solana"|"base", "amount_usdc": float (optional), "transfer_index": int (optional, Solana transfer_index / Base log_index; omitted is first leg)}. Any other chain value is rejected before it ever reaches a query.
walletYesThe wallet these settlement claims are being reported for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoPlain-language caveat on what this report does and doesn't prove.
as_ofNoISO timestamp this report was built. Two reports of the same claims that differ only in tier after a backfill are distinguishable by as_of + classification_version.
cappedNoTrue if claims_requested exceeded max_per_call and extras were dropped.
walletNoThe wallet the claims were submitted for.
verifiedNoPer-claim detail for verified claims, each carrying observed_x402_confidence and observed_facilitator_id.
claimableNoAlways false today — this is a preview, not an on-chain payout unlock.
unverifiedNoPer-claim detail for unverified claims, each with a reason.
max_per_callNoHard cap on claims per call.
score_versionNoReport contract version, e.g. "poecx_bridge_v0".
verified_usdcNoSum of observed USDC for verified claims across all tiers, including excluded. Use verified_usdc_x402_high for allowlist-attributed Base volume.
claims_verifiedNoUnique chain/transaction/leg claims whose wallet and amount matched TWZRD's independently-observed corpus.
claims_requestedNoNumber of claims in the original request, before any cap.
claims_submittedNoNumber of claims actually processed (after cap).
corpus_availableNoFalse when DSN/query failed so claims were not corpus-checked. Distinct from a genuine miss.
attestation_classNo"CORPUS_CROSS_CHECKED" when the corpus was observed; "CORPUS_UNAVAILABLE" when lookup could not run (not a miss). Not TWZRD-attested settlement.
claims_duplicatesNoRepeated chain/transaction/leg claims within the capped input; included in claims_unverified and excluded from value totals.
claims_unverifiedNoClaims not found, with a mismatched wallet or amount, or duplicated within this report.
classification_versionNoBase cluster-pin / KNOWN_CLUSTERS snapshot id. Moves when corpus reclassify changes high/unknown/excluded meaning; distinct from score_version.
verified_usdc_x402_highNoSum of observed USDC for verified claims whose observed_x402_confidence is high (allowlist attribution, not protocol confirmation). Excluded/unknown/untiered are omitted.
verified_usdc_by_confidenceNoVerified USDC split by evidence tier: "high" = relayer funding-cluster is on TWZRD's x402 operator allowlist (attribution, not protocol-level confirmation); "unknown" = observed on-chain transfer TWZRD could not confirm as x402; "excluded" = TWZRD affirmatively classified the settlement as not x402; "untiered" = chain ingest has no confidence tier (Solana).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedOutput schema / properties / as_of
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "ISO timestamp this report was built. Two reports of the same claims that differ only in tier after a backfill are distinguishable by as_of + classification_version.",
      +  "title": "As Of"
      +}
    • changedOutput schema / properties / attestation_class / description
      Previous value: -"\"CORPUS_CROSS_CHECKED\" — verified against TWZRD-observed corpus, not TWZRD-attested settlement."New value: +"\"CORPUS_CROSS_CHECKED\" when the corpus was observed; \"CORPUS_UNAVAILABLE\" when lookup could not run (not a miss). Not TWZRD-attested settlement."
    • addedOutput schema / properties / classification_version
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Base cluster-pin / KNOWN_CLUSTERS snapshot id. Moves when corpus reclassify changes high/unknown/excluded meaning; distinct from score_version.",
      +  "title": "Classification Version"
      +}
    • addedOutput schema / properties / corpus_available
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "False when DSN/query failed so claims were not corpus-checked. Distinct from a genuine miss.",
      +  "title": "Corpus Available"
      +}
    • changedOutput schema / properties / verified_usdc / description
      Previous value: -"Sum of observed USDC for verified claims only. Read verified_usdc_by_confidence before treating this as confirmed x402 volume."New value: +"Sum of observed USDC for verified claims across all tiers, including excluded. Use verified_usdc_x402_high for allowlist-attributed Base volume."
    • changedOutput schema / properties / verified_usdc_by_confidence / description
      Previous value: -"Verified USDC split by evidence tier: \"high\" = confirmed x402 settlement; \"unknown\" = an on-chain transfer TWZRD observed but could not confirm as x402; \"untiered\" = a chain whose ingest has no confidence tier (Solana)."New value: +"Verified USDC split by evidence tier: \"high\" = relayer funding-cluster is on TWZRD's x402 operator allowlist (attribution, not protocol-level confirmation); \"unknown\" = observed on-chain transfer TWZRD could not confirm as x402; \"excluded\" = TWZRD affirmatively classified the settlement as not x402; \"untiered\" = chain ingest has no confidence tier (Solana)."
    • addedOutput schema / properties / verified_usdc_x402_high
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Sum of observed USDC for verified claims whose observed_x402_confidence is high (allowlist attribution, not protocol confirmation). Excluded/unknown/untiered are omitted.",
      +  "title": "Verified Usdc X402 High"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / claims / description
      Previous value: -"Self-reported settlements to cross-check. Each item: {\"tx_signature\": str, \"chain\": \"solana\"|\"base\", \"amount_usdc\": float (optional)}. Any other chain value is rejected before it ever reaches a query."New value: +"Self-reported settlements to cross-check. Each item: {\"tx_signature\": str, \"chain\": \"solana\"|\"base\", \"amount_usdc\": float (optional), \"transfer_index\": int (optional, Solana transfer_index / Base log_index; omitted is first leg)}. Any other chain value is rejected before it ever reaches a query."
    • changedOutput schema / properties / claims_duplicates / description
      Previous value: -"Repeated chain/transaction claims within the capped input; included in claims_unverified and excluded from value totals."New value: +"Repeated chain/transaction/leg claims within the capped input; included in claims_unverified and excluded from value totals."
    • changedOutput schema / properties / claims_verified / description
      Previous value: -"Unique chain/transaction claims whose wallet and amount matched TWZRD's independently-observed corpus."New value: +"Unique chain/transaction/leg claims whose wallet and amount matched TWZRD's independently-observed corpus."
  3. Changed3 schema fields changed
    • addedOutput schema / properties / claims_duplicates
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Repeated chain/transaction claims within the capped input; included in claims_unverified and excluded from value totals.",
      +  "title": "Claims Duplicates"
      +}
    • changedOutput schema / properties / claims_unverified / description
      Previous value: -"Claims not found on-chain, or found with a mismatched amount."New value: +"Claims not found, with a mismatched wallet or amount, or duplicated within this report."
    • changedOutput schema / properties / claims_verified / description
      Previous value: -"Claims whose tx_signature and amount matched TWZRD's independently-observed corpus."New value: +"Unique chain/transaction claims whose wallet and amount matched TWZRD's independently-observed corpus."
  4. Changed3 schema fields changed
    • changedOutput schema / properties / verified / description
      Previous value: -"Per-claim detail for verified claims."New value: +"Per-claim detail for verified claims, each carrying observed_x402_confidence and observed_facilitator_id."
    • changedOutput schema / properties / verified_usdc / description
      Previous value: -"Sum of observed USDC for verified claims only."New value: +"Sum of observed USDC for verified claims only. Read verified_usdc_by_confidence before treating this as confirmed x402 volume."
    • addedOutput schema / properties / verified_usdc_by_confidence
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Verified USDC split by evidence tier: \"high\" = confirmed x402 settlement; \"unknown\" = an on-chain transfer TWZRD observed but could not confirm as x402; \"untiered\" = a chain whose ingest has no confidence tier (Solana).",
      +  "title": "Verified Usdc By Confidence"
      +}
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses extensive behavioral traits beyond annotations: unmatched claims are returned with a reason, cap of 25 with dropped extras, dedup behavior with duplicate handling, preview status with claimable always false, and chain value rejection. This goes far beyond the readOnly and idempotent annotations, adding valuable context for the agent.

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 long but well-structured, opening with the core purpose, then detailing cross-check strength, preview status, cap, and dedup. Every sentence adds necessary information for correct invocation, and it is front-loaded with the most critical purpose.

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 complexity of the tool, including dedup, caps, preview mode, and output schema, the description covers key behaviors: unmatched claims returned, cap behavior, dedup handling, preview status, and chain validation. It also references output fields like `capped`/`claims_requested` and `unverified`, ensuring the agent understands the complete response behavior.

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?

The input schema already provides full descriptions for both parameters, so baseline is 3. The description adds extra semantics for transfer_index dedup key and how duplicates are reported, which goes beyond the schema. It also clarifies that chain values other than solana/base are rejected. This additional context elevates the score to 4.

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's purpose: reporting settlement claims from one's own rails for cross-check against TWZRD's independent corpus. It uses a specific verb ('report') and resource ('settlements'), and distinguishes from sibling tools by explicitly noting 'not TWZRD's paid routes' and that it is a preview. This is specific and not a tautology.

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?

The description provides clear context for when to use this tool: for a real counterparty with settlement volume to feed PoECX, and explicitly notes it is a preview, not an unlock. It also indicates alternatives indirectly by stating 'not TWZRD's paid routes' and references the PoECX plan. However, it does not name specific sibling alternatives, so it gets a 4 rather than 5.

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.