Skip to main content
Glama
Sign In
mcp-guide

mcp-guide

by deeprave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Use Skill

use_skill

Run a named Guide skill by passing its name and parsed option tokens, enabling project guidance workflows and mode-specific instructions.

Instructions

Use a selected Guide skill by name, parsing options through the shared Guide parser.

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.

  • skill (required): string

    • Guide skill name, optionally beginning with $. Do not pass a guide:// URI.

  • args: array[string]

    • Skill option tokens parsed with Guide's shared option parser, such as ['mode=unrelenting', 'verbose'].

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": "use_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYesArguments for the client-facing Guide skill tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but does not disclose what invoking a skill actually does, whether it mutates state, what permissions are required, or what result to expect. It adds some context about the shared parser and opaque session_id handling, but the core execution behavior remains opaque.

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 opening sentence is concise and front-loaded, but the Arguments section duplicates the input schema almost verbatim. That repetition is organized but largely unnecessary given the schema's complete parameter descriptions.

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?

The definition documents the nested inputs and session_id lifecycle well, but with no annotations and no output schema it still leaves the skill's execution effect and return behavior unexplained. It is minimally usable but incomplete for an agent that needs to know what happens after invocation.

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 schema already documents the nested skill, args, and session_id fields. The description mostly restates those same parameter descriptions and adds little semantic meaning beyond them.

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 names a specific verb and resource: use a selected Guide skill by name, with option parsing through the shared Guide parser. It is distinguishable from list_skills, but it does not explicitly contrast itself with that or any other sibling.

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

Usage Guidelines3/5

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

Usage is only implied: the agent must have a selected skill name, and session_id is noted as coming from set_project. There is no explicit when-to-use/when-not guidance or named alternative such as list_skills.

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