Skip to main content
Glama
Sign In
Karbon MCP Server

Karbon MCP Server

by Mad-Man-Dan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create work schedule

create_work_schedule

Create a recurring work schedule from an existing work item to automatically generate new work items based on a defined recurrence pattern.

Instructions

Create a recurring work schedule from an existing work item. The schedule will automatically generate new work items on the recurrence you set — confirm the recurrence details with the user before calling. Note: RecurrenceFrequency cannot be changed after creation.

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": {
      "CreatedFromWorkItemKey": "<CreatedFromWorkItemKey>",
      "RecurrenceFrequency": "<RecurrenceFrequency>",
      "CustomFrequencyMultiple": "<CustomFrequencyMultiple>",
      "ScheduleStartDate": "<ScheduleStartDate>",
      "ScheduleDueDateMethod": "<ScheduleDueDateMethod>",
      "PreventStartEndOnWeekend": "<PreventStartEndOnWeekend>",
      "InitializeTasksBeforeStartDateUnits": "<InitializeTasksBeforeStartDateUnits>",
      "InitializeTasksBeforeStartDateMultiple": "<InitializeTasksBeforeStartDateMultiple>",
      "WorkItemTitleDefinition": "<WorkItemTitleDefinition>"
    },
    "name": "create_work_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
AssigneeUserKeyNoUserKey to assign generated work items to
ScheduleEndDateNoISO 8601 date the schedule stops; omit to run forever
ScheduleStartDateYesISO 8601 date the schedule starts
RecurrenceFrequencyYes
ScheduleDueDateDaysNoThe day count for the due date method (not used with LastDayOfMonth/NoDueDate)
CustomFrequencyUnitsNoOnly when RecurrenceFrequency is Custom
ScheduleDueDateMethodYes
CreatedFromWorkItemKeyYesThe WorkItemKey the schedule is created from
CustomFrequencyMultipleYesMultiple of the frequency unit; use 1 unless RecurrenceFrequency is Custom
WorkItemTitleDefinitionYesTitle format for generated work items; supports Karbon title tokens (e.g. period/date placeholders)
PreventStartEndOnWeekendYesIf true, generated work items never start on a weekend
ScheduleDueDateMonthMultipleNoOnly with DayOfSubsequentMonth: how many months later
InitializeBeforeStartDateUnitsNoCreate the work item this long before its start date
InitializeBeforeStartDateMultipleNo
InitializeTasksBeforeStartDateUnitsYesCreate the work item's tasks/budget this long before its start date
InitializeTasksBeforeStartDateMultipleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A3.9/5.0
Behavior3/5

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

The description discloses that the schedule automatically generates new work items and that RecurrenceFrequency is immutable after creation. With no annotations provided, it adds moderate behavioral context but omits details like required permissions, side effects on existing items, or response behavior.

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 three sentences, each earning its place: first states purpose, second adds behavioral/usage guidance, third adds a critical constraint. No wasted words, front-loaded with the action.

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

Completeness3/5

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

Given the tool's complexity (16 parameters, no output schema), the description covers key behavioral aspects and constraints but omits return value details and does not explain any parameter roles. It is adequate but lacks completeness for a tool this complex.

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 75% (12 of 16 parameters have descriptions), so the baseline is 3. The tool description does not add parameter-specific information beyond what the schema provides, but it does not contradict it.

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 tool creates a recurring work schedule from an existing work item, specifying the resource (work schedule) and action (create). It distinguishes itself from sibling tools like 'create_work_item' and 'update_work_schedule' by focusing on recurrence and schedule generation.

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

Usage Guidelines4/5

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

Provides a clear guideline to 'confirm the recurrence details with the user before calling', which helps ensure proper usage. However, it does not explicitly mention when to avoid using this tool or alternatives beyond the implicit distinction from update.

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