Skip to main content
Glama
boostuagency

combell-mcp-boostu

by boostuagency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

combell_scheduled_tasks_create

Create a scheduled cron job on Linux hosting to run a script at specified times, using a 5-field cron expression and script path.

Instructions

Add a scheduled task (cron job) to a Linux hosting that runs a script on the hosting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledNoDefault true
domain_nameYes
cron_expressionYes5-field cron expression: minute (0-59 or */5, */10, */15, */30), hour (0-23 or *), day of month (1-31 or *), month (1-12 or *), day of week (1-7 = Monday-Sunday, or *). Example: '*/15 * * * *'
script_locationYesAbsolute path on the hosting of the script to execute, e.g. '/www/cron.php'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations are all false (readOnlyHint, idempotentHint, destructiveHint), so the description carries the full burden of behavioral disclosure. It only says 'Add', implying mutation, but provides no detail on side effects, idempotency, error handling, or whether existing tasks with similar configurations are affected.

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, concise sentence that front-loads the action and target. No wasted words, efficient and to the point.

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 4-parameter tool with no output schema, the description is minimal. It doesn't explain the return value, prerequisites, or behavior on success/failure. It also doesn't clarify what domain_name refers to. The cron expression format is in the schema, but other aspects are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 75% of parameters, but the description adds no parameter information. The uncovered domain_name parameter lacks any description in both schema and tool description, so the tool description does not compensate for the gap.

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 clearly states the verb 'Add', the resource 'scheduled task (cron job)', and the target 'Linux hosting'. It distinguishes from sibling list/get/update/delete operations by indicating creation, making the purpose unambiguous.

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 usage for creating a new scheduled task but provides no explicit guidance on when to choose this over update/delete, nor any conditions or alternatives. The action is clear, but no exclusions or sibling comparisons are mentioned.

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