Skip to main content
Glama

Load production craft skill

load_skill
Read-only

Retrieve the full craft playbook and bundled resource list for one or more skill IDs returned by search_skills, so you can apply detailed instructions to a creative task.

Instructions

Load the full craft playbook (SKILL.md) and bundled resource list for one or more skill IDs returned by search_skills.

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

Input Schema

NameRequiredDescriptionDefault
skill_idNoSkill ID to load (e.g. "color-grading-finishing", "caption-typography").
skill_idsNoOptional array of skill IDs to load.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered structurally. The description adds that the return is the full playbook plus a bundled resource list, which helps the agent anticipate payload size, but says nothing about permissions, caching, or how the resource list should be consumed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and the resource, with the sourcing condition attached at the end. No filler or redundancy.

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, read-only, two-parameter tool with annotations and no output schema, this covers purpose, source of IDs, and the shape of the return. The remaining gap is how the bundled resources relate to read_skill_resource, which would round out the model of the skill-loading workflow.

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%, with both skill_id and skill_ids documented including examples, so the schema carries the parameter burden. The only added meaning is "one or more," which hints that multiple IDs are supported but does not clarify whether skill_id and skill_ids are mutually exclusive or additive.

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?

Uses a specific verb ("Load") with a concrete resource ("full craft playbook (SKILL.md) and bundled resource list"), so the agent knows exactly what it gets back. It implicitly separates itself from search_skills by consuming its output, but it never names the closer sibling read_skill_resource, which also retrieves skill content.

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?

The phrase "skill IDs returned by search_skills" establishes the prerequisite workflow (search first, then load), which is the main usage signal. There is no explicit guidance on when to use this versus read_skill_resource, or on when to prefer skill_id over skill_ids, so the when-not side is left to inference.

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