Skip to main content
Glama

List monitoring skills

list_skills

Lists available monitor skills with their rule IDs, units, defaults and ranges so you can set skills and skillAlerts in create_monitor or update_monitor calls.

Instructions

The skills a monitor can carry on this account: extra checks run on every check, each with its own alert rules (speed and Core Web Vitals, SEO, accessibility, broken links, security signals, page problems, third-party scripts, cookies and trackers, SSL certificate and domain expiry). Each entry gives the name for create_monitor/update_monitor skills, the rule ids, units, defaults and ranges for skillAlerts, its options, and locked when the plan does not include it.

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_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (rule ids, units, defaults, ranges for `skillAlerts`, options, `locked`) and a meaningful plan-gating behavior ('`locked` when the plan does not include it'). It does not state read-only status, ordering, or caching, which keeps it off a 5.

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 operative content is front-loaded in the first clause, but the ten-item parenthetical catalog of skill categories (speed/CWV, SEO, accessibility, broken links, security, third-party scripts, cookies, SSL, etc.) is largely decorative for an agent deciding whether to call the tool. The second half about entry fields is the part that earns its place; trimming the enumeration would improve density.

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?

There is no output schema and no annotations, so the description must explain what comes back, and it does so thoroughly, including the `locked` plan caveat. What remains thin is the calling context (that it is account-scoped and parameterless) and any hint of how results relate to list_monitors or list_starter_packs.

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

Parameters4/5

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

The tool takes zero parameters, so there is no input semantics to explain; the baseline for a parameterless tool is 4. The description correctly describes what the entries contain rather than inventing input arguments.

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 names the resource concretely ('the skills a monitor can carry on this account') and defines it in domain terms ('extra checks run on every check, each with its own alert rules'). It implicitly identifies the tool as a catalog/list operation and ties it to create_monitor/update_monitor consumers, but it never explicitly names a sibling list tool as an alternative, so it stops short of full differentiation.

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 implied rather than stated: 'Each entry gives the name for create_monitor/update_monitor `skills`' tells the agent the results feed those write tools, which is real guidance. There is no explicit 'call this before create_monitor to discover valid skill names' instruction and no statement of when not to use it, so the agent must infer the workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.