Ontario Protocol

Refresh an x402 Service Profile

ontario_refresh-listing

Use only for an existing paid Ontario provider profile when the caller wants a fresh live readiness observation attached to its canonical HTML, JSON twin, and badge. This tool cannot edit provider metadata, improve a grade by payment, or buy ranking or traffic. Do not pay while the launch passport's 30-day included maintenance is active. Agent payment guidance: run free can-pay and readiness checks first; pay only when policy allows base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and 0.10 USDC is inside the agent budget. [PAID: 0.10 USDC via x402 on Base. Two-step flow: call without payment to receive MCP PaymentRequired, then retry with params._meta['x402/payment'] containing the signed PaymentPayload. The legacy _x402_payment base64 argument is also supported. Sign only after explicit budget and policy approval.]

Input Schema

TableJSON Schema

Name	Required	Description
`listing_id`	Yes	Existing paid provider profile id.
`_x402_payment`	No	base64 x402 PaymentPayload (USDC on Base); obtain the requirements by calling this tool without it first.
`paid_refresh_tx`	No	One-use retry reference only when a settled refresh could not complete.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "buyer_guide": {
+          "format": "uri",
+          "type": "string"
+        },
+        "hint": {
+          "type": "string"
+        },
+        "payment_policy": {
+          "format": "uri",
+          "type": "string"
+        },
+        "payment_required": {
+          "const": true
+        },
+        "x402": {
+          "type": [
+            "object",
+            "string"
+          ]
+        }
+      },
+      "required": [
+        "payment_required",
+        "x402",
+        "hint"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": true,
+      "properties": {
+        "boundary": {
+          "description": "Payment buys a new observation, not a better grade or guaranteed discovery.",
+          "type": "string"
+        },
+        "listing": {
+          "properties": {
+            "id": {
+              "pattern": "^lst_[A-Za-z0-9_-]+$",
+              "type": "string"
+            },
+            "verification": {
+              "type": "object"
+            },
+            "verification_status": {
+              "enum": [
+                "ready",
+                "close",
+                "needs_work",
+                "pending"
+              ]
+            }
+          },
+          "required": [
+            "id",
+            "verification_status",
+            "verification"
+          ],
+          "type": "object"
+        },
+        "payment": {
+          "description": "Settlement or one-use retry reference, never a wallet signing secret.",
+          "type": "object"
+        },
+        "profile": {
+          "properties": {
+            "evidence": {
+              "type": "object"
+            },
+            "listing": {
+              "type": "object"
+            },
+            "schema": {
+              "const": "ontario.x402_listing_profile.v1"
+            }
+          },
+          "required": [
+            "schema",
+            "listing",
+            "evidence"
+          ],
+          "type": "object"
+        },
+        "provider_next_steps": {
+          "required": [
+            "schema",
+            "boundary"
+          ],
+          "type": "object"
+        },
+        "status": {
+          "const": "refreshed"
+        }
+      },
+      "required": [
+        "status",
+        "payment",
+        "listing",
+        "profile",
+        "provider_next_steps",
+        "boundary"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description clearly discloses the paid two-step x402 flow, PaymentRequired retry behavior, legacy _x402_payment support, and budget/policy approval requirements. This goes well beyond the annotations' false readOnlyHint and false idempotentHint, and nothing contradicts the annotations.

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 front-loaded with scope and purpose, then restrictions, then payment guidance. It is dense and contains slight redundancy in the payment approval instructions, but every major detail serves a real decision: when to pay, how to pay, and what not to expect.

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?

For a paid, state-changing refresh tool with an output schema present, the description covers the essential agent knowledge: eligibility, non-goals, included maintenance caveat, free-check-first workflow, exact payment amount/chain, two-step retry protocol, and approval gating. Nothing critical for correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful payment-flow semantics beyond the schema: calling without payment first, retrying with params._meta['x402/payment'], and the legacy _x402_payment base64 argument. This improves agent understanding of how to populate and use the payment-related parameter.

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 verb/resource ('fresh live readiness observation attached to canonical HTML, JSON twin, and badge') and limits use to 'an existing paid Ontario provider profile.' It also differentiates from siblings by listing what the tool cannot do: edit metadata, improve grade by payment, or buy ranking/traffic.

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?

It gives explicit when-to-use ('existing paid Ontario provider profile' needing a fresh readiness observation), when-not-to-use ('cannot edit provider metadata... Do not pay while the launch passport's 30-day included maintenance is active'), and alternative behavior ('run free can-pay and readiness checks first'). The paid flow conditions are clearly stated.

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.