Skip to main content
Glama

Save skill draft

save_skill_draft
DestructiveIdempotent

Save a complete AI-authored skill package as a Draft in the active vault. Creates a new skill or a new version; never scans, submits, approves or releases it.

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": {
      "files": "<files>",
      "idempotency_key": "<idempotency_key>",
      "mode": "<mode>"
    },
    "name": "save_skill_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
filesYes
idempotency_keyYes
expected_draft_idNo
target_skill_slugNo
expected_draft_updated_atNo

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is partly covered. The description adds useful lifecycle context (writes only a Draft, never submits or releases), but it says nothing about what the destructive hint means in practice, how the idempotency key governs retries, or what happens when a draft already exists.

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?

Two short sentences, action first, scope second, with no filler. Every clause carries information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with six parameters and zero schema documentation, the description is thin: it omits concurrency expectations, retry/idempotency behavior and the relationship between mode, target_skill_slug and the expected_* fields. An output schema exists, so return values need not be explained, but the input-side gaps remain significant.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description carries the full explanatory burden and does not meet it. "Creates a new skill or a new version" loosely maps to the mode enum, but idempotency_key, target_skill_slug, expected_draft_id and expected_draft_updated_at — which look like optimistic-concurrency and conflict-resolution controls — are never mentioned.

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 ("Save a complete AI-authored skill package as a Draft in the active vault") and adds negative scope that excludes scanning, submitting, approving and releasing. That gives an agent a clear picture of the operation, though it never names a concrete sibling to contrast with, so differentiation is implied rather than explicit.

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?

"Creates a new skill or a new version" ties usage to the mode choice, and the closing clause rules out publishing-type operations. However, there are no explicit preconditions (e.g. that a full file set must already be authored, or when to prefer a new version over a create) and no alternative tool is named for the excluded 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.

Resources