Skip to main content
Glama
Sign In
SkillForge

SkillForge

by CatVinci-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_skills

Retrieve all available skills with names and descriptions. Review each skill to capture domain-specific guidance and avoid repeating past mistakes before starting a task.

Instructions

🔴 MANDATORY FIRST CALL — Call this before starting ANY task.

Returns all available skills with name and description. Review each description — if relevant to your current task, call get_skill to load full instructions.

WHY: Skills encode hard-won conventions and user preferences. Skipping this step means you will miss domain-specific guidance and repeat mistakes that have already been corrected.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It describes a read-only operation returning skill names and descriptions, with no side effects. Lacks details on rate limits or authentication, but for a simple list call, this is adequate.

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?

Six sentences with emoji and emphasis. Front-loaded with mandatory call. Every sentence adds value, though could be slightly more terse. Overall efficient and well-structured.

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

Completeness5/5

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

Zero parameters, output schema exists, and siblings listed. Description fully covers why to call, what it returns, and what action to take next. No gaps given the tool's simplicity.

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?

No parameters exist; schema coverage is 100%. Description adds no param info because none needed. Baseline of 4 for zero parameters is appropriate.

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?

The description clearly states the tool returns all available skills with name and description, and emphasizes it's a mandatory first call. It distinguishes itself from the sibling get_skill by directing users to call that for full instructions.

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

Usage Guidelines5/5

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

Explicitly states 'MANDATORY FIRST CALL — Call this before starting ANY task.' Provides clear context for when to use (always first) and directs to get_skill for relevant skills. Explains WHY to skip would cause missing guidance.

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