Skip to main content
Glama

Create Skill

create_skill

Create a new skill from a blank slate (origin: user_authored) — requires Pro Plus. Pro can fork an existing skill instead with fork_skill. description is required (1-1024 chars) — it is the only signal an agent uses to decide when to load the skill, so name specific trigger phrases and a "do NOT use for..." case.

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": {
      "scope": "<scope>",
      "name": "<name>",
      "description": "<description>",
      "body": "<body>"
    },
    "name": "create_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesPlain CommonMark instructions — no templating or interpolation
nameYesKebab-case, <= 64 chars, e.g. "my-writing-style"
scopeYes
titleNo
auto_loadNo
descriptionYesRequired, 1-1024 chars — the sole signal an agent uses to decide when to load this skill
project_keyNoRequired when scope is "project"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent write, so the description usefully adds the plan/entitlement gate ("requires Pro Plus") and the origin value that will be stamped on the record. It does not discuss name-collision behavior, whether auto_load changes retrieval, or what the response contains, which keeps it short of a 5.

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?

A single dense sentence plus an em-dash clause; the creation mode and plan requirement are front-loaded before the field advice. Nothing is redundant, though the nested parenthetical and quoted guidance make it slightly harder to scan than it could be.

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 7-parameter mutation with no output schema, the description covers the entitlement gate and the most consequential field but omits scope selection, auto_load semantics, and how project_key interacts with scope. An agent could still call it, but would be guessing on three parameters.

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 coverage is 57%, and the description only elaborates on the description field (already documented in the schema as the sole load signal), adding triggering-phrase and anti-trigger advice. The three uncovered parameters (scope, title, auto_load) get no explanation, notably scope, whose required 'project' value pairs with project_key.

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?

States a specific verb and resource ("Create a new skill") plus the creation mode ("from a blank slate (origin: user_authored)"), and explicitly distinguishes itself from fork_skill, which is the closest sibling for the same resource. An agent can tell create from fork without opening either schema.

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?

Gives a clear routing rule: blank-slate creation here, forking an existing skill via fork_skill, and a plan precondition (Pro Plus vs Pro). It does not address update_skill or get_skill, but the primary alternative is named with its condition, so guidance is concrete rather than implied.

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.