Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Create Ai Skill

create_ai_skill

Create a reusable AI skill from a name, description, and markdown body, then control whether the model, users, or automations can load it.

Instructions

Create an AI skill from a name, description and markdown body. invocable_by controls who may load it: the model, users, automations. An AI skill is reusable written guidance (markdown body) that Rootly AI agents, users and AI automations can load while they work. Skills keep saved versions, readable with list_ai_skill_versions.

Requires OAuth scope ai.skills:write. Read-only attributes are ignored on write.

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": {
      "data": "<data>"
    },
    "name": "create_ai_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent open-world write. The description adds real value beyond them: the required OAuth scope `ai.skills:write`, the fact that skills retain saved versions, and that read-only attributes are silently ignored on write. It does not say what happens on name/slug collisions or how errors surface.

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?

It is front-loaded with the action and required inputs, then the concept, then the operational constraints, which is a sensible order for an agent. The parenthetical '(markdown `body`)' appears twice and the skill definition sentence is slightly redundant, but nothing is seriously bloated.

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 an output schema present, return values need no explanation, and the description covers auth scope, the meaning of the key parameter, and the existence of versions. For a single nested create call it is nearly complete; only collision/duplicate-name behavior and the effect of enabled=false are left unstated.

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 reported at 0%, so the description must carry parameter meaning; it does explain the three required fields and, notably, that invocable_by governs who may load the skill (model, users, automations), which is more than the enum alone conveys. It says nothing about slug, enabled, or owner_user_id, leaving those to the schema.

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?

The description opens with a specific verb and resource ('Create an AI skill from a name, description and markdown body') and defines what a skill is, so the agent knows exactly what the tool produces. It distinguishes the version-reading path by naming list_ai_skill_versions, but does not explicitly contrast with update_ai_skill.

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?

It gives useful context ('reusable written guidance that Rootly AI agents, users and AI automations can load'), which implies when a skill is appropriate, and explains the invocable_by decision. However, there is no explicit when-to-use / when-not-to-use guidance versus update_ai_skill when a skill already exists, and no prerequisites beyond the OAuth scope line.

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