Skip to main content
Glama

List skills

list_skills

List all skills (name, category, description), optionally filtered by category and/or AI model family.

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
modelNoOptional AI model family filter: chatgpt (ChatGPT), claude (Claude), gemini (Gemini), grok (Grok), llama (Llama), deepseek (DeepSeek), mistral (Mistral), qwen (Qwen), kimi (Kimi K). Skills written for "any" AI match every family.
provenNoOptional. true limits results to skills marked works-on-5-models: the latest logged result is a pass on 5+ AI families within 365 days.
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "frontend",
      -  "backend",
      -  "deployment",
      -  "debugging",
      -  "design",
      -  "coding-prompts",
      -  "writing-prompts",
      -  "research-prompts",
      -  "marketing-prompts"
      -]New value: +[
      +  "frontend",
      +  "backend",
      +  "deployment",
      +  "debugging",
      +  "design",
      +  "coding-prompts",
      +  "writing-prompts",
      +  "research-prompts",
      +  "marketing-prompts",
      +  "apps",
      +  "ai-agents"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / model / description
      Previous value: -"Optional AI model family filter: chatgpt (ChatGPT), claude (Claude), gemini (Gemini), grok (Grok), llama (Llama), deepseek (DeepSeek), mistral (Mistral), qwen (Qwen). Skills written for \"any\" AI match every family."New value: +"Optional AI model family filter: chatgpt (ChatGPT), claude (Claude), gemini (Gemini), grok (Grok), llama (Llama), deepseek (DeepSeek), mistral (Mistral), qwen (Qwen), kimi (Kimi K). Skills written for \"any\" AI match every family."
    • changedInput schema / properties / model / enum
      Previous value: -[
      -  "chatgpt",
      -  "claude",
      -  "gemini",
      -  "grok",
      -  "llama",
      -  "deepseek",
      -  "mistral",
      -  "qwen"
      -]New value: +[
      +  "chatgpt",
      +  "claude",
      +  "gemini",
      +  "grok",
      +  "llama",
      +  "deepseek",
      +  "mistral",
      +  "qwen",
      +  "kimi"
      +]
  3. Changed3 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "frontend",
      -  "backend",
      -  "deployment",
      -  "debugging",
      -  "prompts",
      -  "design"
      -]New value: +[
      +  "frontend",
      +  "backend",
      +  "deployment",
      +  "debugging",
      +  "design",
      +  "coding-prompts",
      +  "writing-prompts",
      +  "research-prompts",
      +  "marketing-prompts"
      +]
    • addedInput schema / properties / model
      Added value: +{
      +  "description": "Optional AI model family filter: chatgpt (ChatGPT), claude (Claude), gemini (Gemini), grok (Grok), llama (Llama), deepseek (DeepSeek), mistral (Mistral), qwen (Qwen). Skills written for \"any\" AI match every family.",
      +  "enum": [
      +    "chatgpt",
      +    "claude",
      +    "gemini",
      +    "grok",
      +    "llama",
      +    "deepseek",
      +    "mistral",
      +    "qwen"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / proven
      Added value: +{
      +  "description": "Optional. true limits results to skills marked works-on-5-models: the latest logged result is a pass on 5+ AI families within 365 days.",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the return fields and that filters are optional, which signals a safe, unfiltered enumeration. However it says nothing about result ordering, pagination, or whether large result sets are truncated.

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?

One compact sentence with the resource and returned fields front-loaded and the optional filters trailing. Dense but no wasted words; a brief phrase on ordering would have cost little.

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?

For a simple filtered-list tool with no output schema, listing the returned fields is genuinely useful and covers the essentials. The absence of ordering, result-size, and cross-reference-to-search guidance leaves it only minimally complete.

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 67% and the description adds little beyond it: it restates category/model filtering but never mentions the 'proven' parameter, whose behavior is documented only in the schema. It also uses 'AI model family' where the parameter is named 'model', a minor naming gap the enum description bridges.

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?

States a specific verb and resource ('List all skills') and even enumerates the returned fields (name, category, description). It does not distinguish itself from search_skills or list_categories, so sibling differentiation is left to the agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage cue is that filtering by category and/or model is optional. There is no guidance on when to use this versus search_skills (keyword search) or list_categories, and no exclusions or prerequisites are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.