Skip to main content
Glama

Load a Berrys creative playbook

playground_skill_load
Read-onlyIdempotent

Load exact versioned instructions. Built-in skills need no projectId. Private project skills require projectId and scope: project, with current read access. Does not generate media or grant permissions.

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": {
      "id": "<id>",
      "version": "<version>"
    },
    "name": "playground_skill_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSkill ID returned by skills_discover.
scopeNoSkill scope returned by skills_discover; project skills require projectId.
versionYesExact version returned by discovery for the selected operation or skill.
projectIdNoProject ID for project-specific access or skills; omit for general capabilities or built-in skills.

Output Schema

NameRequiredDescriptionDefault
idYes
scopeYes
titleYes
summaryYes
versionYes
instructionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds value by disclosing the exact-version requirement, the access prerequisite ('current read access'), and explicit non-behaviors. It stops short of describing what the loaded payload looks like or how large it may be, but the output schema covers returns.

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?

Three short sentences, front-loaded with the action, then the access rule, then the exclusion. No filler, though the opening sentence is slightly abstract without the title to anchor what an 'instruction' is.

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?

With annotations, a 100%-covered schema, an output schema, and only four flat parameters, the description supplies everything needed to call it correctly: the prereq for project skills and the explicit non-capabilities. Only a pointer to the discovery tool as the source of id/version is missing from the description text.

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 baseline is 3. The description restates the key conditional (projectId + scope: project for private skills, omitted for built-in) but adds no format or coupling detail beyond what the schema properties already say.

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?

States a specific verb+resource: 'Load exact versioned instructions', and the scope ('built-in' vs 'private project skills') makes clear it fetches a versioned skill payload. It does not name the discovery sibling explicitly (that link only appears in the schema's parameter descriptions), so it stops short of full sibling differentiation.

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 concrete conditions for each mode: built-in skills need no projectId, while private project skills require projectId, scope: project, and current read access. It also states an exclusion ('does not generate media or grant permissions'), though it never routes the agent to an alternative tool for those actions.

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.