Skip to main content
Glama
altrsoftware

ALTR MCP Server

Official
by altrsoftware

create_sc_agent_task

Create a scheduled task for an agent to run against a repository. Configure classifier or SIS agent tasks with type-specific parameters and a cron schedule.

Instructions

Create a task for an agent.

A task runs against a specific repo on a schedule. Configuration depends on agent type (check with get_sc_agent first).

CLASSIFIER agent configuration:

  • classification_type: must be 5

  • sample_strategy: "ROWS" or "PERCENT"

  • collection_name: classifier collection name Do NOT include SIS fields (service_name, audit_file_path, etc.) for classifier agents.

SIS (audit) agent configuration varies by DB:

  • Oracle: optional 'initial_audit_timestamp', 'service_name'

  • MSSQL: 'audit_file_path' (required, absolute path)

  • PostgreSQL: 'audit_file_path', 'audit_file_type' (log/csv/json), optional 'log_line_prefix'

  • MySQL: either 'table_name' or 'audit_file_path' Do NOT include classifier fields for SIS agents.

Schedule: 'type' ("CRON"), 'value' (cron expression), optional 'max_duration' (ISO 8601), optional 'timezone' (e.g. "America/New_York").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesAgent UUID.
nameYesTask name.
repo_nameYesTarget repository name.
configurationYesAgent-type-specific config dict or JSON string. See above for required fields.
scheduleYesSchedule dict or JSON string.
descriptionNoOptional task description.
service_userNoService user for auth. Required for Oracle, MSSQL, MySQL (table_name mode). Forbidden for PostgreSQL and MySQL (audit_file_path mode).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It reveals that configuration depends on agent type, explains schedule format, and notes conditional service_user requirements. However, it does not disclose potential side effects, permissions, or error conditions.

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?

The description is structured into clear sections and front-loads the main purpose. It is comprehensive but slightly lengthy; every sentence earns its place, though minor trimming could improve conciseness.

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

Completeness5/5

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

Given the tool's complexity (7 params, conditional logic), the description thoroughly covers all parameters and usage scenarios. An output schema exists, so return values need not be explained. Contextually complete.

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?

Schema description coverage is 100%, but the description adds significant meaning: it explains the configuration structure per agent type, schedule format, and service_user conditions, far exceeding schema descriptions.

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 'Create a task for an agent' and specifies that the task runs against a specific repo on a schedule. It distinguishes from sibling tools like delete_sc_agent_task, update_sc_agent_task, and list_sc_agent_tasks by focusing on creation and configuration details.

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?

The description provides explicit when-to-use guidance, including checking agent type with get_sc_agent first. It details configuration per agent type (CLASSIFIER vs SIS) and specifies fields to include or avoid, serving as clear alternatives.

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/altrsoftware/altr-mcp-server'

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