Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Get Ai Skill

get_ai_skill
Read-only

Fetch a single AI skill by ID or slug, including its current markdown body, to load reusable guidance for Rootly AI agents and automations. Read-only.

Instructions

Get one AI skill by id, including its current body. Read-only. 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:read.

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": {
      "id": "<id>"
    },
    "name": "get_ai_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe skill ID or slug.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry readOnlyHint/destructiveHint/openWorldHint, and the description reinforces read-only plus adds genuinely new context: the required OAuth scope `ai.skills:read` and the fact that the returned payload includes the current `body`. It doesn't describe error behavior for unknown ids, but the auth-scope disclosure is real value beyond the annotations.

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?

Three tight sentences: the operation is front-loaded, then the domain concept, then the version alternative and auth requirement. No filler or repetition of the title.

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?

For a single-parameter read tool with an output schema, the definition covers scope, return content (`body`), access requirements, and the relevant version-related sibling. Nothing critical is missing, though a note on behavior for invalid ids or slugs would close the last gap.

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 coverage is 100% and the `id` field is documented as accepting an ID or slug. The description only says 'by id' and adds no syntax or format guidance, so the schema does the heavy lifting — the baseline 3 applies.

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?

States a specific verb and resource ('Get one AI skill by id, including its current `body`'), and defines what an AI skill is (reusable markdown guidance loaded by Rootly AI agents/users). This separates it from the sibling list/get-version tools without requiring the schema to be opened.

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?

Makes the use case explicit: fetch a single skill's current body, and routes to `list_ai_skill_versions` when saved versions are needed. It stops short of naming when-not to use it (e.g., prefer `get_ai_skill_version` for a pinned historical version), so context is clear but exclusions are incomplete.

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