Omniyond

schedule_job

Schedule an HTTP request to run once or on a recurring interval (e.g. every 5m/1h/1d). Each run is prepaid from your credit balance. Returns the job id, status and remaining balance.

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": {
      "url": "<url>"
    },
    "name": "schedule_job"
  }
}

Input Schema

Name	Required	Description	Default
`pay`	No	When true, the scheduler pays the target endpoint via x402 (USDC on Base) on each run from Omniyond's operator wallet, up to maxPriceUsd. Lets an agent schedule a job that itself buys a paid API. Requires an API key with prepaid credits.
`url`	Yes	The URL the job will call (http/https, public hosts only).
`body`	No	Optional request body (string).
`runAt`	No	ISO timestamp for the first run. Defaults to now.
`method`	No	HTTP method.	POST
`headers`	No	Optional request headers.
`maxRuns`	No	For recurring jobs: how many runs to prepay (each run costs the per-run fee).
`delivery`	No	Where results go: stored for retrieval, POSTed to callbackUrl, or both.	store
`schedule`	No	Recurrence interval like "5m", "1h", "1d". Omit for a one-shot job. Minimum 5m.
`callbackUrl`	No	URL to POST each run result to (required for callback delivery).
`maxPriceUsd`	No	Max USD the scheduler will pay the downstream API per run when pay=true. Defaults to $0.10, hard-capped at $1.00. Reserved per run from your credits; unspent reservation is refunded on cancel.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does add real value by disclosing the prepaid credit billing model and the return payload (job id, status, remaining balance), but it omits auth/credit prerequisites, failure/retry behavior, and what happens to unused prepaid runs.

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 short sentences with no waste: purpose first, cost model second, return contract third. Every sentence earns its place and nothing is buried.

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 an 11-parameter mutation tool with no annotations and no output schema, the description usefully covers the billing model and the return values, which the missing output schema would otherwise leave undefined. It falls short on auth/credit prerequisites and error behavior, but the schema fills most parameter detail.

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% across all 11 parameters, including enums for method/delivery and the pay/maxPriceUsd payment semantics, so the schema already does the heavy lifting. The description adds only the recurrence example ('5m/1h/1d') and the one-shot default, which the schema also states.

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?

Specific verb and resource ('Schedule an HTTP request') plus the two operating modes (one-shot vs recurring interval). The purpose is unambiguous, but it never names or contrasts with the lifecycle siblings (cancel_job, restart_job, get_job), so sibling differentiation is left to inference.

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?

Usage is implied: you use it when you need an HTTP call run once or repeatedly on an interval. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as cancel_job or restart_job for job management.

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

All Omniyond 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.

Resources

Need Help?