noticed

create_scheduled_task

Create recurring noticed agent work. Every occurrence runs the same prompt in a new noticed chat. Use an ISO future timestamp for 'at', milliseconds for 'every' (minimum 60000), or a 5-6 part cron expression for 'cron'.

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": {
      "name": "<name>",
      "schedule_kind": "<schedule_kind>",
      "schedule_value": "<schedule_value>",
      "prompt": "<prompt>"
    },
    "name": "create_scheduled_task"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Human-readable task name.
`prompt`	Yes
`enabled`	No
`timezone`	No
`schedule_kind`	Yes
`schedule_value`	Yes

Output Schema

Name	Required	Description
`ok`	Yes	Whether noticed completed the operation.
`data`	No	The operation result when ok is true.
`error`	No	A human-readable error when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

AddedAug 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description adds meaningful side-effect context beyond annotations: every occurrence creates a new noticed chat and runs the same prompt. It also discloses formatting constraints such as future timestamps, a 60000 ms minimum, and cron-part counts. This is helpful behavioral detail even though the annotations already indicate this is a non-read-only, non-idempotent mutation.

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?

The description is three sentences with no filler. It front-loads the core purpose and packs the critical schedule encoding rules into the remaining sentences, making it easy to scan and apply.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the scheduling semantics well and there is an output schema so return values do not need to be explained. Still, it does not address timezone handling, the enabled flag's default behavior, or how the three schedule kinds interact with timezone, which are meaningful gaps for a scheduled-task creation tool.

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?

With only 17% schema description coverage, the description must compensate, and it does for the most complex parameter: schedule_value. It precisely explains ISO timestamps for 'at', milliseconds for 'every', and 5-6 part cron expressions for 'cron'. However, timezone and enabled parameters receive no semantic guidance, leaving a small but notable gap.

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?

The description clearly states the tool creates a recurring scheduled task and specifies that each occurrence runs the same prompt in a new noticed chat, distinguishing it from update/list/delete siblings. The phrase 'noticed agent work' is somewhat jargon-heavy, which prevents a 5.

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?

The description implies this tool is for creating recurring scheduled work, but it never explicitly tells the agent when to use this tool versus update_scheduled_task or delete_scheduled_task. The schedule-format guidance is useful but is parameter-level guidance, not tool-selection guidance.

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

All noticed 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?