Skip to main content
Glama

List skills

list_skills
Read-onlyIdempotent

Retrieve read-only JSON lists of Skills Studio preferences and folders for the active or specified workspace, with a configurable result limit.

Instructions

List Skills Studio preferences and folders. Skills are imported as JSON packs, not SQLite inserts. Read-only. Returns JSON skills and folders.

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
limitNoMaximum rows. Integer from 1 to 500. Default 100.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows. Integer from 1 to 500. Default 100."
  3. Addedv6.1.5

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already establish a read-only, idempotent, non-destructive operation, so “Read-only” adds nothing beyond the structured fields. The only additional context is that skills are imported as JSON packs rather than SQLite inserts, which has limited relevance to invoking a list call; behaviors such as result truncation or workspace visibility are not otherwise explained.

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 description is short and front-loads the action, but not every sentence earns its place. “Read-only” duplicates the annotations, the return sentence overlaps the opening and output schema, and the SQLite aside consumes space without resolving the preferences-versus-skills wording.

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 read-only list tool with no required parameters, complete input descriptions, and an output schema, this is mostly sufficient to select and invoke it. The inconsistent resource wording and lack of explicit selection guidance prevent full marks, but no major calling prerequisite appears to be missing.

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?

Both parameters are fully documented in the schema, including the limit’s bounds and default and the workspace’s name, slug, ID, and active-workspace behavior. The description adds no parameter meaning, so the 100% schema coverage supports the baseline score.

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 uses a concrete list verb and identifies Skills Studio content, with the result described as skills and folders. It does not distinguish itself from sibling listing tools, and “preferences and folders” versus “skills and folders” leaves the exact resource scope slightly inconsistent.

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?

The Skills Studio context implies using the tool to inspect that area, but there is no explicit when-to-use condition, prerequisite, or comparison with another listing tool. The JSON-pack sentence discusses import mechanics rather than helping the agent select this operation.

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