Skip to main content
Glama
Sign In
GoClaw MCP Server

GoClaw MCP Server

by nextlevelbuilder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

goclaw_cron_create

Create scheduled cron jobs to automate agent tasks with specified timing, agent assignment, and message content.

Instructions

Create a new cron job

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>",
      "expression": "<expression>",
      "agent_id": "<agent_id>",
      "message": "<message>"
    },
    "name": "goclaw_cron_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesJob name
expressionYesCron expression (e.g. '0 */6 * * *')
agent_idYesAgent ID to run the job with
messageYesMessage to send to the agent
enabledNoEnable on creation (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Create a new cron job' implies a write/mutation operation but reveals nothing about permissions required, whether creation is idempotent, what happens on duplicate names, rate limits, or what the response contains. For a mutation tool with zero annotation coverage, this is inadequate.

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, efficient sentence with zero wasted words. It's front-loaded with the essential action and resource, making it immediately scannable. Every word earns its place in this minimal but complete statement of purpose.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., does it return the created job ID?), error conditions, or system behavior. The agent lacks crucial context about how this tool actually operates in the system.

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%, with all parameters clearly documented in the schema itself. The description adds no additional parameter context beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'Create a new cron job' clearly states the action (create) and resource (cron job), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like goclaw_cron_update or goclaw_custom_tool_create, which also involve creation operations but for different resources.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing an existing agent), comparison to goclaw_cron_update for modifications, or when cron jobs are appropriate versus other scheduling methods. The agent must infer usage from the tool name alone.

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

Deploy Server

Other Tools