Skip to main content
Glama
Sign In

Ontario Protocol

by com.ontarioprotocol
OverviewDiscussionsAdmin

Ontario Validate Refresh

ontario_validate-refresh

Check an existing paid provider profile's refresh eligibility for free, including cooldown. Never refreshes, signs or spends.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listing_id": "<listing_id>"
    },
    "name": "ontario_validate-refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYesExisting paid provider profile id.
paid_refresh_txNoOne-use retry reference for a settled refresh that could not complete.

Output Schema

NameRequiredDescriptionDefault
okYes
errorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / paid_refresh_tx / description
      Previous value: -"One-use retry reference only when a settled refresh could not complete."New value: +"One-use retry reference for a settled refresh that could not complete."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

The description adds concrete behavioral guarantees beyond the annotations: no refresh, no signing, no spending, plus the existence of a cooldown check. This matters because readOnlyHint=false and idempotentHint=false leave the agent unsure how safe the call is; the explicit 'never spends/refreshes' resolves that. It does not say what state the call does touch (the reason readOnlyHint is false).

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?

Two sentences, both front-loaded: the first states what it does and that it is free; the second eliminates the three risks an agent would worry about. No padding.

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?

An output schema exists, so return shape need not be explained, and the safety profile and cooldown mention cover the main behavioral unknowns for a 2-parameter validation tool. Only the interaction with ontario_refresh-listing and the retry reference's role in a validation check are left unstated.

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 both parameters (listing_id, paid_refresh_tx) are already documented in the schema. The description adds no parameter-level meaning, which is acceptable given full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'check ... refresh eligibility' on 'an existing paid provider profile' — which an agent can distinguish from the sibling ontario_refresh-listing. It does not name that sibling explicitly, so the negative-space framing is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'for free' and 'Never refreshes' imply this is the side-effect-free pre-check before a paid refresh, but no alternative (ontario_refresh-listing) is named and no explicit when-to-use or when-not-to-use condition is given. Usage must be inferred.

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

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

Resources