Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

schedule_asset_execution

Automate recurring compliance assessments by scheduling asset execution with custom cron expressions, control periods, and duration settings.

Instructions

Schedule automated execution for a asset.

IMPORTANT WORKFLOW & SAFETY RULES:

  • User inputs (runPrefixName, cronTab) are mandatory and cannot be bypassed or assumed.

  • The cronTab string MUST be constructed explicitly from the user's schedule instructions (e.g., frequency, time-of-day, timezone). Never auto-generate it without user confirmation.

  • controlPeriod MUST be one of the supported values.

  • controlDuration MUST be a positive integer provided by the user. Args:

    • assetId (str): Id of the asset to be scheduled.

    • runPrefixName (str): Human-readable name/prefix for this scheduled run.

    • description (str): Description for the scheduled run.

    • cronTab (str): Full cron expression including timezone (e.g. TZ=Asia/Calcutta 0 0 * * *), explicitly provided/confirmed by the user. Must not be assumed or defaulted.

    • controlPeriod (str): Control period for the assessment run, type selected by the user. Allowed values: - DAY → Last few days - WEEK → Last few weeks - MONTH → Last few months - CAL_WEEK → Last few calendar weeks - CAL_MONTH → Last few calendar months

    • controlDuration (int): Duration count for the selected control period Returns:

    • success (bool): Indicates if the schedule was created successfully.

    • scheduleId (str): ID of the created schedule (only present if successful).

    • error (Optional[str]): An error message if any issues occurred during creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYes
runPrefixNameYes
descriptionYes
cronTabYes
controlPeriodYes
controlDurationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses critical behavioral traits (user confirmation required, persistent schedule creation via scheduleId return) and validation constraints, though could explicitly state this creates a recurring job that runs automatically.

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?

Well-structured with safety rules front-loaded, though slightly redundant (cronTab and controlPeriod constraints repeated between safety section and Args section).

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?

Comprehensive coverage given complexity and lack of schema descriptions; includes Returns section and validation rules, though could briefly reference sibling management tools (delete_asset_schedule, list_asset_schedules).

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

Parameters5/5

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

Exceptional compensation for 0% schema coverage with detailed Args section including cronTab example, allowed controlPeriod enum values with semantic meanings, and explicit constraints for each parameter.

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?

States clear purpose (schedule automated execution) but could specify it creates recurring assessment runs rather than generic 'execution' to better distinguish from immediate execution siblings like execute_task.

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

Usage Guidelines5/5

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

Excellent explicit safety rules and workflow constraints (mandatory user inputs, no auto-generation of cronTab, validation requirements) that clearly define when and how to use the tool correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ComplianceCow/cow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server