ProLevelMax

Schedule a repeating run (paid per run)

procli_schedule_create

Creates a daily or weekly scheduled run of a data source at a set time (Beijing time), e.g. a daily check of Reddit mentions of a brand. Each run is charged like a normal run and never costs more than runCap. Without confirmed=true it returns a preview (cost cap per run, monthly maximum, first run time) and saves nothing; with confirmed=true it saves the schedule. Schedules can also be viewed, paused and deleted in the console (dashboard → Schedules).

Input Schema

Name	Required	Description
`time`	Yes	Time of day, 24-hour "HH:MM", Beijing time (UTC+8), e.g. "09:00"
`input`	Yes	Input fields for this source
`runCap`	No	Most one run may cost, in USD. Default: the source's quote for this input
`scraper`	Yes	Source id, e.g. "procli_reddit_c"
`weekday`	No	Weekly only: the day to run
`maxItems`	No	Per-result sources: most results per run (default 100)
`confirmed`	No	true saves the schedule; false or absent returns the preview only
`frequency`	Yes	How often to run
`monthlyCap`	No	Optional: most this schedule may spend per calendar month, in USD
`notifyEmail`	No	Email the user when each run finishes (count, cost, link to the run)

Output Schema

Name	Required	Description
`next`	No	What to do next
`saved`	Yes	false = preview only, nothing saved; true = saved
`manage`	No	Where to manage schedules
`preview`	No	What would be saved, with summary
`schedule`	No	A repeating run

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 22, 2026

changedInput schema / properties / confirmed / description

Previous value: -"true only after the user agreed to the cost shown in the preview"New value: +"true saves the schedule; false or absent returns the preview only"

changedInput schema / properties / input / description

Previous value: -"Input fields for this source (see procli_inspect)"New value: +"Input fields for this source"

changedInput schema / properties / scraper / description

Previous value: -"Source id from procli_discover"New value: +"Source id, e.g. \"procli_reddit_c\""

changedOutput schema / properties / saved / description

Previous value: -"false = preview only, ask the user and call again with confirmed=true; true = saved"New value: +"false = preview only, nothing saved; true = saved"

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (which only say it is a non-idempotent, non-destructive write), the description discloses the cost model — each run is billed like a normal run and is capped by runCap — and that the preview mode saves nothing and returns cost cap per run, monthly maximum, and first run time. That is exactly the money/permission context an agent needs before invoking a paid mutation.

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?

Front-loaded with purpose and frequency/timezone, then the cost model, then the preview-vs-save contract. Information-dense with no filler; the only marginally off-topic sentence is the closing console note, which is short and still useful for lifecycle awareness.

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?

With 10 parameters, an output schema, and full annotation coverage, this description still supplies everything not in structured fields: billing model, cap semantics, preview contents and the no-save guarantee, timezone, and post-creation management path. Nothing needed to call it correctly 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, but the description adds real meaning: it ties runCap to a hard per-run ceiling, links monthlyCap to a monthly maximum surfaced in the preview, and explains that confirmed controls persistence. It also reinforces the Beijing-time constraint on the time 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?

Specific verb + resource + scope: creates a daily or weekly scheduled run of a data source at a set time in Beijing time, with a concrete example. This is clearly distinguishable from procli_run (one-off) and procli_schedule_list/delete without opening any schema.

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 clearly frames the two modes of use (preview when confirmed is absent/false, save when true) and mentions that viewing/pausing/deleting happens in the console, steering the agent away from using this tool for lifecycle management. However, it never explicitly names procli_run as the alternative for a single non-repeating run.

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

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