Skip to main content
Glama
Rootly MCP server

Rootly MCP server

Official
by rootlyhq

List Ai Skills

list_ai_skills
Read-only

List a team's AI skills with details like name, slug, description, who may invoke each, and enabled status. Supports sorting and filtering to find reusable guidance quickly.

Instructions

List the team's AI skills: name, slug, description, who may invoke each and whether it is enabled. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ai_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
filter_slugNo
filter_searchNo
filter_sourceNo
filter_enabledNo
filter_invocable_byNoComma-separated sources; skills matching any listed source are returned.
filter_created_at_gtNo
filter_created_at_ltNo
filter_created_at_gteNo
filter_created_at_lteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=true), so this is not the description's burden. The description nonetheless adds genuinely non-structured behavior: the required OAuth scope `ai.skills:read`, the semantic meaning of a skill as loadable markdown `body`, and the existence of saved versions. It does not disclose pagination or result-size behavior for a list call, which is the main remaining gap.

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 sentences, front-loaded with the verb and returned fields, followed by a compact domain definition and the auth requirement. Nothing is padded and every sentence adds information an agent would otherwise lack.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, the description needn't explain return values, and its safety/auth story is solid. The material gap is the ten-parameter filter surface, eight of which are undocumented in both schema and description — for a list tool whose main difficulty is filtering, that is a real completeness shortfall.

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

Parameters2/5

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

Schema description coverage is only 10% (10 parameters, only filter_invocable_by documented), so the description must carry filter semantics and it largely does not. It implicitly gestures at two filters by naming "who may invoke each" and "whether it is enabled", but sort ordering, filter_search, filter_source, filter_slug, and the four created_at range bounds are left with no meaning beyond their parameter names.

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 team's AI skills") and enumerates the fields returned (name, slug, description, invocability, enabled state). It also defines the domain object (reusable written markdown guidance loaded by agents/users/automations) and points to list_ai_skill_versions for version history, so an agent can distinguish it from that sibling without opening either schema.

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?

Declares the operation read-only and routes version-history needs to list_ai_skill_versions, which gives clear context for when this tool is the right one. It does not state any explicit exclusions (e.g. that this is team-scoped rather than cross-workspace, or when to prefer get_ai_skill for a single skill), so it falls short of the full when/when-not/alternatives bar.

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