Skip to main content
Glama

list_skills

List a project's available skills with names and descriptions so you can identify which one to load when a task matches.

Instructions

List the project's skills: name and description. Load one with get_skill before relying on it, only when your task matches its description.

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
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.8/5.0
Behavior3/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 disclose that results are limited to name and description summaries rather than full skill content. It says nothing about scope (are skills global, per-project, or both?), the effect of an empty project value, or result volume/ordering.

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?

Two short sentences with zero filler, and the core action is front-loaded before the follow-up guidance. Nothing is redundant or padded.

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?

An output schema exists, so return-value description is not required, and the safety profile of a read-only listing is implicit. However, for a tool whose only input is a scoping parameter, leaving that parameter's semantics unexplained is a meaningful completeness gap.

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?

The single parameter 'project' has 0% schema description coverage and a default of empty string, yet the description never mentions it or explains whether omitting it lists across all projects. The agent must guess the meaning of the only input it can supply.

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 project's skills") and even the return fields (name and description). It explicitly distinguishes itself from the sibling get_skill by positioning that tool as the follow-up loader rather than an alternative lister.

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?

Gives a clear two-step workflow: list here, then load a chosen skill with get_skill "only when your task matches its description", which is a usable selection condition. It stops short of saying when not to call this tool, e.g. how it relates to catalog_list or other list_* tools.

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