Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

Register Verification Catalog

register_verification_catalog
Destructive

Register any x402 service's signed. use it rather than create_audit_evidence_package for verification catalog, not audit evidence package; an object with 47 fields including algorithm, canonicalSha256. $0.25 USDC.

Input Schema

NameRequiredDescriptionDefault
claimNoThe claim this operation operates on. See the schema for its type and whether it is required.
edgesNoThe edges this operation operates on. See the schema for its type and whether it is required.
signatureNoThe Ed25519 signature to verify, base64-encoded.
service_urlNoThe service url this operation operates on. See the schema for its type and whether it is required.
claim_sha256NoThe claim sha256 this operation operates on. See the schema for its type and whether it is required.
service_nameNoThe service name this operation operates on. See the schema for its type and whether it is required.

Output Schema

NameRequiredDescriptionDefault
urlNoThe `url` field of the response.
kindNoThe `kind` field of the response.
nameNoThe `name` field of the response.
noteNoA note on how the answer was produced.
edgesNoThe `edges` field of the response.
valueNoThe `value` field of the response.
claimsNoThe `claims` field of the response.
detailYesHuman-readable explanation of the verdict.
sha256NoThe `sha256` field of the response.
framingNoThe `framing` field of the response.
metricsNoThe `metrics` field of the response.
verdictYesThe decision this tool returned.
coverageNoHow much of the underlying corpus the answer is based on.
signedByNoThe `signedBy` field of the response.
algorithmNoThe `algorithm` field of the response.
indexedAtNoThe `indexedAt` field of the response.
integrityNoThe `integrity` field of the response.
referenceNoThe `reference` field of the response.
trustTierNoThe `trustTier` field of the response.
claimCountNoThe `claimCount` field of the response.
ed25519SigNoThe `ed25519Sig` field of the response.
serviceUrlNoThe `serviceUrl` field of the response.
trustIndexNoThe `trustIndex` field of the response.
trust_tierNoThe `trust_tier` field of the response.
claimSha256NoThe `claimSha256` field of the response.
claim_countNoThe `claim_count` field of the response.
serviceNameNoThe `serviceName` field of the response.
trust_indexNoThe `trust_index` field of the response.
url_presentNoThe `url_present` field of the response.
evidenceCoreNoThe `evidenceCore` field of the response.
name_presentNoThe `name_present` field of the response.
observationsNoThe `observations` field of the response.
publicKeyHexNoThe `publicKeyHex` field of the response.
verdictLevelNoThe `verdictLevel` field of the response.
edges_skippedNoThe `edges_skipped` field of the response.
networkDegreeNoThe `networkDegree` field of the response.
evidenceDigestNoThe `evidenceDigest` field of the response.
network_degreeNoThe `network_degree` field of the response.
canonicalSha256NoThe `canonicalSha256` field of the response.
reproducibilityNoThe `reproducibility` field of the response.
edges_registeredNoThe `edges_registered` field of the response.
recomputedSha256NoThe `recomputedSha256` field of the response.
sig_format_validNoThe `sig_format_valid` field of the response.
signaturePresentNoThe `signaturePresent` field of the response.
verificationHintNoThe `verificationHint` field of the response.
signature_presentNoThe `signature_present` field of the response.
claim_sha256_suppliedNoThe `claim_sha256_supplied` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed49 schema fields changed
    • addedOutput schema / properties / algorithm
      Added value: +{
      +  "description": "The `algorithm` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / canonicalSha256
      Added value: +{
      +  "description": "The `canonicalSha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / claimCount
      Added value: +{
      +  "description": "The `claimCount` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / claimSha256
      Added value: +{
      +  "description": "The `claimSha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / claim_count
      Added value: +{
      +  "description": "The `claim_count` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / claim_sha256_supplied
      Added value: +{
      +  "description": "The `claim_sha256_supplied` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / claims
      Added value: +{
      +  "description": "The `claims` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / coverage
      Added value: +{
      +  "description": "How much of the underlying corpus the answer is based on.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / detail
      Added value: +{
      +  "description": "Human-readable explanation of the verdict.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / ed25519Sig
      Added value: +{
      +  "description": "The `ed25519Sig` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / edges
      Added value: +{
      +  "description": "The `edges` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / edges_registered
      Added value: +{
      +  "description": "The `edges_registered` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / edges_skipped
      Added value: +{
      +  "description": "The `edges_skipped` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / evidenceCore
      Added value: +{
      +  "description": "The `evidenceCore` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / evidenceDigest
      Added value: +{
      +  "description": "The `evidenceDigest` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / framing
      Added value: +{
      +  "description": "The `framing` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / indexedAt
      Added value: +{
      +  "description": "The `indexedAt` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / integrity
      Added value: +{
      +  "description": "The `integrity` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / kind
      Added value: +{
      +  "description": "The `kind` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / metrics
      Added value: +{
      +  "description": "The `metrics` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / name
      Added value: +{
      +  "description": "The `name` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / name_present
      Added value: +{
      +  "description": "The `name_present` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / networkDegree
      Added value: +{
      +  "description": "The `networkDegree` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / network_degree
      Added value: +{
      +  "description": "The `network_degree` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / note
      Added value: +{
      +  "description": "A note on how the answer was produced.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / observations
      Added value: +{
      +  "description": "The `observations` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / publicKeyHex
      Added value: +{
      +  "description": "The `publicKeyHex` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / recomputedSha256
      Added value: +{
      +  "description": "The `recomputedSha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reference
      Added value: +{
      +  "description": "The `reference` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / reproducibility
      Added value: +{
      +  "description": "The `reproducibility` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / serviceName
      Added value: +{
      +  "description": "The `serviceName` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / serviceUrl
      Added value: +{
      +  "description": "The `serviceUrl` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sha256
      Added value: +{
      +  "description": "The `sha256` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / sig_format_valid
      Added value: +{
      +  "description": "The `sig_format_valid` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signaturePresent
      Added value: +{
      +  "description": "The `signaturePresent` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signature_present
      Added value: +{
      +  "description": "The `signature_present` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / signedBy
      Added value: +{
      +  "description": "The `signedBy` field of the response.",
      +  "type": "object"
      +}
    • removedOutput schema / properties / status
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / trustIndex
      Added value: +{
      +  "description": "The `trustIndex` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / trustTier
      Added value: +{
      +  "description": "The `trustTier` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / trust_index
      Added value: +{
      +  "description": "The `trust_index` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / trust_tier
      Added value: +{
      +  "description": "The `trust_tier` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / url
      Added value: +{
      +  "description": "The `url` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / url_present
      Added value: +{
      +  "description": "The `url_present` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / value
      Added value: +{
      +  "description": "The `value` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verdict
      Added value: +{
      +  "description": "The decision this tool returned.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / verdictLevel
      Added value: +{
      +  "description": "The `verdictLevel` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / properties / verificationHint
      Added value: +{
      +  "description": "The `verificationHint` field of the response.",
      +  "type": "object"
      +}
    • addedOutput schema / required
      Added value: +[
      +  "detail",
      +  "verdict"
      +]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the safety hints (destructive/non-readonly), the description adds critical operational data: the payload size (47 fields) and the cost ($0.25 USDC). These are vital behavioral traits for an agent making business or resource-constrained decisions.

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 extremely dense and efficient. It packs the core purpose, sibling comparison, payload details, and operational cost into one highly effective sentence without any wasted words.

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?

The tool is highly complete. It informs the agent about its identity, its functional difference from competitors, its resource usage (cost/fields), and its scope, providing all necessary context before parameter inspection.

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?

Since schema description coverage is 100%, the schema already provides complete information on all 6 parameters. The description does not add any semantic meaning or constraints to the input fields themselves.

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 tool clearly states its primary function: registering a signed x402 service artifact. It explicitly defines the resource and distinguishes itself from a key sibling, providing immediate context for the agent.

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?

The description acts as a perfect usage guide by giving a clear directive: use this tool for 'verification catalog' and specifically *not* `create_audit_evidence_package` for that same purpose. This prevents common misrouting.

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.