Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Ai Skill Versions

list_ai_skill_versions
Read-only

List the saved versions of an AI skill, newest first, to review changes and trace updates. Read-only; requires the ai.skills:read OAuth scope.

Instructions

List the saved versions of one AI skill, newest first. 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": {
      "ai_skill_id": "<ai_skill_id>"
    },
    "name": "list_ai_skill_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
ai_skill_idYesThe skill ID or slug.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' largely repeats structured data. It earns credit for disclosing the required OAuth scope `ai.skills:read` and the newest-first result ordering, though it says nothing about pagination or result limits on a list operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core statement is front-loaded and efficient, but the middle sentence defining what an AI skill is and the closing 'readable with list_ai_skill_versions' restate the name rather than adding actionable information. Two of four sentences could be trimmed with no loss.

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?

An output schema exists, so return structure needn't be explained, and the auth scope plus ordering are covered. Given the tool's simplicity, the definition is essentially complete; only pagination behavior for a list call is unaddressed.

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 already documents the single `ai_skill_id` parameter as accepting an ID or slug. The description only implies the parameter via 'one AI skill' and adds no syntax or format detail beyond the schema, so the baseline of 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 ('List the saved versions of one AI skill') plus the ordering guarantee ('newest first'). That scope cleanly separates it from the single-version sibling and from list_ai_skills without needing to name them.

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?

Usage is only implied: you call it when you want the version history of a known skill. There is no explicit guidance on when to prefer it over get_ai_skill_version or get_ai_skill, and no prerequisite note that a skill must already exist.

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