Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

Get Ai Skill Version

get_ai_skill_version
Read-only

Retrieve a specific saved version of an AI skill, including its markdown body, to inspect or compare prior guidance. Read-only and requires the ai.skills:read scope.

Instructions

Get one saved version of an AI skill, including the body it had at that version. 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>",
      "version": "<version>"
    },
    "name": "get_ai_skill_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesRequired. Value for `{version}` in /v1/ai/skills/{ai_skill_id}/versions/{version}.
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

A4.1/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' is largely redundant, but the description adds genuinely new context: the required OAuth scope `ai.skills:read` and the fact that the returned content includes the historical markdown body. It does not describe error behavior for a nonexistent version, which is a minor gap given a single-item read.

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?

Front-loaded with the operation and its distinguishing return field, then the domain gloss on what a skill is, then the scope requirement. The definitional aside about skills is somewhat long for a getter, but it earns its place for an agent unfamiliar with the resource.

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 only two fully documented parameters, a present output schema, and annotations covering the safety profile, the description supplies the missing auth requirement and the meaning of the returned body. Only the failure mode for an invalid version/skill ID is left unspecified.

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 100%, so both `ai_skill_id` and `version` are already documented, and the description adds no format syntax, versioning rules, or lookup semantics beyond restating that `version` selects a saved version. Baseline 3 applies when the schema carries the parameter burden.

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 saved version of an AI skill') and pins the distinguishing payload: the `body` at that version. It also defines what an AI skill is and names the sibling (list_ai_skill_versions) that handles the list case, so an agent can separate it from get_ai_skill and list_ai_skill_versions without opening schemas.

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?

Clearly frames the retrieval context and routes version enumeration to list_ai_skill_versions, which is the correct prerequisite for obtaining a `version` value. It stops short of explicit when-not guidance (e.g., use get_ai_skill instead if you need the current/latest body), so routing is implied rather than fully enumerated.

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