Ontario Protocol

Validate an x402 Service Listing Free

ontario_validate-service

Free provider listing preflight. Validate public service metadata before buying the 0.50 USDC Ontario launch passport. Returns field errors or a normalized request and publication decision. Set verify_now only to create a public readiness report. Never publishes a listing, signs or spends; a valid payload alone does not establish readiness or Bazaar placement.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Public service name displayed on the provider profile.
`tags`	No	Public capability tags for discovery, up to ten relevant labels.
`asset`	No	Payment token contract accepted by the provider on the declared network.
`method`	No	HTTP method used to call the provider's endpoint.	POST
`source`	No	Privacy-safe aggregate acquisition bucket; never a URL or query.	direct_or_unknown
`network`	No	Provider payment network, for example base or eip155:8453. Ontario publication itself uses Base USDC.	base
`category`	No	Public capability category for the service, not a claim of certification.
`endpoint`	Yes	Provider-owned public HTTPS x402 endpoint to list. Never include secrets or sensitive query parameters.
`owner_url`	No	Public website identifying the provider; publication does not verify legal identity.
`price_usdc`	Yes	Provider endpoint price in decimal USDC, at most six decimal places. This is separate from Ontario's 0.50 USDC publication fee.
`verify_now`	No	Optionally run live readiness checks and save a public signed report. No listing is published and no payment is made.
`buyer_query`	No	Public task phrase used for the point-in-time Bazaar retrieval audit. It may appear in the public profile.
`description`	Yes	Public buyer task, expected result, and important service limitations; do not include confidential text.
`price_atomic`	No	Optional provider price in six-decimal USDC units: 10000 equals 0.01 USDC. Must match price_usdc when supplied.
`owner_contact`	No	Optional provider contact retained for operations and omitted from public profiles. Omit when unnecessary; never send wallet credentials.
`mcp_remote_url`	No	Optional public MCP remote for read-only initialize and tools/list checks.
`mcp_server_name`	No	Optional exact MCP Registry server name.
`mcp_server_json_url`	No	Optional public MCP Registry record or exact-search JSON URL.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`errors`	Yes
`warnings`	Yes
`next_steps`	Yes
`normalized`	Yes
`verification`	Yes	Optional public readiness observation; metadata validation alone does not verify readiness.
`stores_listing`	Yes
`trust_disclaimer`	Yes
`provider_publication`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "errors": {
+      "maxItems": 0,
+      "type": "array"
+    },
+    "next_steps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "normalized": {
+      "required": [
+        "name",
+        "description",
+        "endpoint",
+        "price_usdc",
+        "network"
+      ],
+      "type": "object"
+    },
+    "ok": {
+      "const": true
+    },
+    "provider_publication": {
+      "properties": {
+        "decision": {
+          "enum": [
+            "paid_publication_available",
+            "fix_readiness_before_purchase",
+            "run_free_verification"
+          ]
+        },
+        "price": {
+          "type": "object"
+        },
+        "purchase": {
+          "type": "object"
+        },
+        "schema": {
+          "const": "ontario.provider_publication_product.v1"
+        }
+      },
+      "required": [
+        "schema",
+        "decision",
+        "price",
+        "purchase"
+      ],
+      "type": "object"
+    },
+    "stores_listing": {
+      "const": false
+    },
+    "trust_disclaimer": {
+      "type": "string"
+    },
+    "verification": {
+      "description": "Optional public readiness observation; metadata validation alone does not verify readiness.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "warnings": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ok",
+    "errors",
+    "warnings",
+    "normalized",
+    "verification",
+    "provider_publication",
+    "stores_listing",
+    "trust_disclaimer",
+    "next_steps"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description discloses nontrivial side effects and limitations: no listing publication, no signing or spending, verify_now optionally creates a public readiness report, and a valid payload alone does not establish readiness or Bazaar placement. This goes well beyond the annotations, which only provide general hints.

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?

Three sentences are packed with necessary information and no filler. The main purpose is front-loaded with 'Free provider listing preflight,' followed by timing, return behavior, and explicit safety exclusions. Every sentence earns its place.

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 complex tool with 18 parameters, the description gives the essential decision framework: when to call, what happens, what does not happen, and how verify_now changes behavior. The output schema covers return values, and the 100% schema coverage covers parameters, so nothing critical is missing. It could still briefly point to the named sibling publishing tool, but the guidance is otherwise complete.

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 100%, so the input schema already documents all 18 parameters. The description adds useful context about the overall flow, such as the 0.50 USDC fee and the preflight role, but it does not add per-parameter meaning beyond the schema. Baseline 3 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 states a specific verb and resource: validate public service metadata as a free preflight before the Ontario launch passport purchase. It clearly distinguishes the tool from the listing/publishing siblings by saying it never publishes a listing, signs, or spends.

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 gives clear timing context: use it before buying the 0.50 USDC launch passport. It also explains the conditional use of verify_now and explicitly excludes publishing/signing/spending. It does not name the sibling tool ontario_list-service as the alternative for actually publishing, but the exclusion is clear enough.

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

All Ontario Protocol 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.