Skip to main content
Glama
runwhen-contrib

RunWhen Platform MCP

create_chat_command

Create a chat slash-command for workspace chat, with optional cron-based scheduling and automatic delivery of results to email or Slack.

Instructions

Create a chat command (slash-command). Name must be alphanumeric, underscore, or hyphen only.

Skill: runwhen-skill://manage-commands (scoping, scheduling, sinks).

Commands are invoked in chat as /label.

To run a command on a schedule, set cron_schedule plus sink_configs, run_as_user, and assistant_name. Results are delivered to each sink (email or Slack) when the cron fires.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCommand name (alphanumeric, underscore, or hyphen only).
max_runsNoMaximum scheduled runs before the schedule stops (omit for unlimited).
scope_idNoScope ID (null for platform; workspace name for workspace).
is_activeNoWhether the command is active.
scope_typeYesOne of platform, org, workspace, persona, user.
descriptionNoOptional description for the command.
run_as_userNoEmail of the user the scheduled session runs as. Required when cron_schedule is set.
sink_configsNoDelivery targets when cron_schedule is set. Each entry: {type: 'email'|'slack', mode: 'user'|'all-workspace-users'|'channel'|'webhook', target: '...'}.
cron_scheduleNoCron expression to run this command on a schedule (e.g. '0 8 * * 1-5'). When set, also provide sink_configs, run_as_user, and assistant_name.
assistant_nameNoPersona for scheduled runs (workspace prefix optional). For persona-scoped commands, must match scope_id (full form after PAPI). For workspace-scoped commands, use the short name (persona_name for chat).
workspace_nameYesThe workspace to create the command in (e.g. 't-oncall').
command_contentYesMarkdown content of the command.
schedule_pausedNoWhen true, the cron does not fire (independent of is_active).
auto_approve_readonlyNoWhen true, scheduled runs auto-approve read-only task execution (write tasks still require approval).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses naming constraints, invocation syntax, and scheduling behavior, but omits details on permissions, idempotency, or what happens on duplicate names.

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 very concise, with only five lines, front-loading the core purpose. Every sentence adds meaningful information without redundancy.

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?

With 14 parameters and an output schema, the description covers essential creation and scheduling aspects. It does not explain all parameters, but the schema handles them. Additional context on skill and invocation is helpful.

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

Parameters4/5

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

Schema description coverage is 100%, baseline 3. The description adds value by explaining the relationship between scheduling parameters and the skill context, going beyond the schema's individual parameter 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 the tool creates a chat command (slash-command) and specifies naming constraints. This verb+resource combination effectively distinguishes it from sibling tools like create_assistant or create_chat_rule.

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 provides guidance on when to set scheduling parameters (cron_schedule plus sink_configs, run_as_user, assistant_name) but does not explicitly indicate when to use this tool over alternatives or when not to use it.

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/runwhen-contrib/runwhen-platform-mcp'

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