Friday MCP Server

list_skills

List installed skills and check their activation state to manage skill availability on the server.

Instructions

List installed skills and their activation state.

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

Name	Required	Description	Default
`active_only`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Implementation Reference

src/friday_mcp_server/tools/skills.py:12-14 (handler)

MCP tool handler for list_skills. Decorated with @mcp.tool() and delegates to SkillStore.list_skills().

def list_skills(active_only: bool = False) -> list[dict]:
    """List installed skills and their activation state."""
    return skill_store.list_skills(active_only=active_only)

src/friday_mcp_server/tools/skills.py:12-12 (schema)
Input schema: accepts optional boolean active_only parameter. Returns list of dicts.
```
def list_skills(active_only: bool = False) -> list[dict]:
```

src/friday_mcp_server/skill_store.py:52-57 (helper)

Core business logic: loads the registry JSON, optionally filters for active skills, returns sorted list.

def list_skills(self, active_only: bool = False) -> list[dict[str, Any]]:
    registry = self._load_registry()
    records = sorted(registry.values(), key=lambda item: item["id"])
    if active_only:
        records = [item for item in records if item["active"]]
    return records

src/friday_mcp_server/tools/skills.py:10-11 (registration)
Registration via @mcp.tool() decorator inside the register function, called by register_all_tools.
```
def register(mcp, *, skill_store) -> None:
    @mcp.tool()
```
src/friday_mcp_server/tools/__init__.py:11-12 (registration)
Bridge call: register_all_tools invokes skills.register(), which registers the list_skills tool on the MCP server.
```
skills.register(mcp, skill_store=skill_store)
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 26, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations exist, so description must cover behavior; only mentions listing state but omits whether it's read-only, performance impact, or any side effects.

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?

Single sentence is concise and front-loaded, but too brief to cover essential details; earns a mid score for minimal verbosity.

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

Completeness2/5

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

Despite output schema and simple input, description omits parameter behavior and any usage context; incomplete for practical use by an agent.

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

Parameters1/5

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

Schema description coverage is 0% for the single parameter 'active_only'; description does not explain its purpose or effect, failing to compensate for lack of schema documentation.

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?

Clearly states 'List installed skills and their activation state' – a specific verb+resource that distinguishes from siblings like activate/deactivate/get_skill.

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?

No guidance on when to use this tool vs alternatives like get_skill or search; no indication of prerequisites or context for active_only parameter.

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