Skip to main content
Glama

Promote Draft

promote_draft

Moves a draft skill from drafts/<skill_name> into skills/ and reindexes the catalog, requiring explicit human approval before promotion.

Instructions

Move drafts/<skill_name> para skills/ e reindexa. Exige aprovação humana explícita.

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": {
      "skill_name": "<skill_name>"
    },
    "name": "promote_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose three real traits: a mutation (moving files out of drafts/), a side effect (reindexing), and a hard gating requirement (explicit human approval). It stops short of saying what happens if a skill of the same name already exists in skills/ or whether the move is reversible.

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 sentences, no filler, with the operation front-loaded and the approval gate placed as a trailing constraint where it belongs. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained, and the description covers the core action, its side effect, and its precondition. For an un-annotated file-moving mutation it should still say whether an existing target is overwritten and what happens on failure, which an agent needs before invoking it.

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?

The schema has a single required parameter with zero description coverage, so the description must compensate partially. It does, by showing that skill_name identifies a directory under drafts/ (drafts/<skill_name>), which clarifies the expected value format. It does not state naming constraints or validation rules.

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 and resource path: moves drafts/<skill_name> into skills/ and reindexes. That is concrete enough to distinguish it from propose_skill_draft (which presumably creates the draft) without opening schemas, though the mixed Portuguese/Spanish phrasing ('para ... e reindexa') adds slight friction for a non-Iberian agent.

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 precondition 'requires explicit human approval' implies the tool is used only after a draft has been reviewed and a human has signed off, which is meaningful usage context. However, it never states when to use this versus siblings such as rebuild_index (which also reindexes) or propose_skill_draft, and no exclusions are given.

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