Skip to main content
Glama
Sign In
mcp-guide

mcp-guide

by deeprave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Skills

list_skills

Lists available Guide skills and entrypoint URIs for availability checks. Select a skill, then retrieve its URI before applying instructions; use verbose or table for a user-facing catalogue.

Instructions

List Guide-provided skills and their explicit entrypoint URIs.

By default the catalogue is agent information for availability checks. Pass verbose=true for a user-facing catalogue or table=true for a user-facing Markdown table. Select a listed skill and retrieve its entrypoint URI before applying that skill's instructions.

Arguments

  • session_id: string | null

    • Opaque Guide interaction identifier returned by set_project. Pass it through unchanged on later tool, prompt, and resource calls. Do not construct, alter, or treat it as a FastMCP transport session id.

  • verbose: boolean

    • Return a user-facing catalogue instead of agent-only availability information

  • table: boolean

    • Return the user-facing catalogue as a Markdown table

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "args": "<args>"
    },
    "name": "list_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYesArguments for list_skills tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the three output modes, the agent-vs-user-facing distinction, and the important session_id handling rules. It still leaves some behavioral details implicit, such as confirmation that the operation is purely read-only and what the catalogue structure looks like.

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 purpose and mode guidance are front-loaded, but the separate Arguments section duplicates parameter descriptions already present at full coverage in the schema. That repetition adds length without adding much information.

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 simple three-argument listing tool with no output schema, the description covers the main modes, session identifier semantics, and the intended retrieval workflow. It is broadly complete, though it could say more about the returned catalogue shape or error behavior.

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 100%, so the input schema already documents session_id, verbose, and table. The Arguments section largely repeats those schema descriptions rather than adding new parameter semantics beyond the defaults already shown.

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 gives a specific verb and resource: it lists Guide-provided skills and their explicit entrypoint URIs. That is clear enough to distinguish it from generic collection tools, though it does not explicitly name a sibling alternative.

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?

It explains the default use case as an agent availability check, says when to use verbose and table modes, and tells the agent to select a skill and retrieve its entrypoint URI before applying instructions. It does not provide explicit when-not guidance or name alternative tools.

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