AgentsID Guard

Official

by AgentsID-dev

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

cron_add

Add a cron job to run commands on a schedule, with cron.write permission required for secure execution.

Instructions

Add a cron job. Requires cron.write permission.

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": {
      "schedule": "<schedule>",
      "command": "<command>"
    },
    "name": "cron_add"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	Command to run
`schedule`	Yes	Cron schedule (e.g., '0 * * * *' for hourly)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose the required cron.write permission, which is useful for authorization. It does not mention duplicate handling, schedule validation, or what the operation returns, but for a simple add operation this is acceptable.

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 a single, front-loaded sentence that immediately states the action. The permission requirement is included as an essential qualifier, and there is no wasted or redundant phrasing.

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 a two-required-parameter creation tool with 100% schema coverage and no output schema, the description provides the essential action and permission context. It could be slightly more complete by mentioning that created jobs can be listed with cron_list, but this is not necessary for selection or invocation.

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?

The input schema already provides full descriptions for both parameters ('Command to run' and 'Cron schedule with an example'), so the description adds no extra meaning beyond what the schema defines. Baseline 3 is appropriate because the schema carries the parameter semantics.

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?

The description states a clear action and resource: 'Add a cron job.' It is concise and distinct from the sibling tools cron_list and cron_remove, so an agent can easily differentiate when to use this tool.

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 intended usage is implied by the verb 'Add' and the resource 'cron job,' and the permission requirement gives a prerequisite. However, it does not explicitly mention alternatives or scenarios where another tool would be preferred, so guidance is adequate but not detailed.

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