Ontario Protocol

Match a public task to an Ontario tool

ontario_task_fit

Free task-to-tool matching with an optional Jev second opinion. With allow_typesafe=true, your public task and Ontario's public tool descriptions are sent to TypeSafe for Jev inference. Do not supply secrets, personal data, private URLs, or customer content. Ontario does not persist task text here. TypeSafe processing is subject to its policies; zero retention is not promised. Without consent, only Ontario's deterministic router is used. Returns a callable tool and input schema, or abstains. Never executes tools or authorizes payment. Model quota exhaustion falls back to deterministic routing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`task`	Yes	A public capability request, never private task content.
`network`	No	Network permitted by the caller's wallet policy; Ontario paid tools require Base mainnet (eip155:8453).	eip155:8453
`max_usdc`	No	Explicit owner-approved USDC ceiling; never inferred.
`allow_typesafe`	No	With allow_typesafe=true, your public task and Ontario's public tool descriptions are sent to TypeSafe for Jev inference. Do not supply secrets, personal data, private URLs, or customer content. Ontario does not persist task text here. TypeSafe processing is subject to its policies; zero retention is not promised. Without consent, only Ontario's deterministic router is used.
`wallet_enabled`	No	True only when the caller can locally sign an x402 payment; this flag does not authorize spending.
`free_preflight_complete`	No	True only after the recommended free check has completed for this task.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`payment_authorized`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 23, 2026

addedInput schema / properties / free_preflight_complete / description

Added value: +"True only after the recommended free check has completed for this task."

addedInput schema / properties / network / description

Added value: +"Network permitted by the caller's wallet policy; Ontario paid tools require Base mainnet (eip155:8453)."

addedInput schema / properties / wallet_enabled / description

Added value: +"True only when the caller can locally sign an x402 payment; this flag does not authorize spending."

AddedSep 21, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Discloses data flow: with allow_typesafe=true, task and tool descriptions go to TypeSafe; warns not to supply secrets; states Ontario does not persist task text; mentions TypeSafe policies and zero retention not promised; says never executes tools or authorizes payment; fallback on quota exhaustion. This is rich behavioral disclosure beyond 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 a single dense paragraph with all sentences contributing safety, mode, or behavior details. It's longer than minimal but each clause is necessary.

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?

Covers purpose, data handling, safety, return value, and fallback. With an output schema present and thorough parameter descriptions, nothing essential is missing.

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 descriptions are exhaustive for all six parameters (100% coverage), and the tool description does not add further parameter semantics beyond what the schema already states.

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?

Description states 'Free task-to-tool matching with an optional Jev second opinion' and clarifies it 'Returns a callable tool and input schema, or abstains.' This clearly defines the action and resource, and distinguishes it from sibling tools that target specific functions (e.g., find_x402_tool, ontario_purchase_router).

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 implies usage as a generic matcher but doesn't explicitly contrast with siblings. Mentions optional Jev second opinion and deterministic router, giving context on when each mode is used, but no explicit 'use this when...' guidance. However, the clarity of its role as a matcher is sufficient.

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.