Skip to main content
Glama

Propose Skill Draft

propose_skill_draft

Saves a human-confirmed skill draft to drafts//SKILL.md for review before promotion, keeping unverified skills out of the active skills directory.

Instructions

Salva um RASCUNHO de skill em drafts//SKILL.md (nunca em skills/).

Só chame depois de o humano confirmar explicitamente que quer o rascunho. content é o corpo em Markdown; um frontmatter enviado junto é mesclado.

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": {
      "name": "<name>",
      "description": "<description>",
      "content": "<content>"
    },
    "name": "propose_skill_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
contentYes
descriptionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the write target, the prohibition on writing to skills/, the human-confirmation requirement, and the non-obvious merge behavior for frontmatter. It stops short of stating what happens if a draft with the same name already exists (overwrite? error?) or what the response contains, though an output schema exists to cover the latter.

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 write destination and the safety constraint, then the precondition, then the content semantics. Nothing is padding, though the frontmatter remark reads as an aside that could be tied more explicitly to an input field.

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 three-required-parameter write tool with no annotations but an output schema, the description covers destination, precondition, and content semantics adequately; return values need not be explained. The remaining gap is collision/overwrite behavior and any constraint on what a valid `name` may contain, which matter for a tool that constructs a filesystem path.

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 0%, so the description must compensate for three parameters, and it only partly does: `content` is defined as the Markdown body, but `name` and `description` are never explained. The mention of a "frontmatter enviado junto" being merged is behaviorally useful but ambiguous here, since no frontmatter parameter exists among name/content/description, leaving the agent to guess how description relates to frontmatter fields.

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 ("Salva um RASCUNHO de skill") plus the exact destination path drafts/<name>/SKILL.md, and explicitly rules out the sibling location ("nunca em skills/"). An agent can immediately tell this apart from promote_draft, which is what moves a draft into skills/.

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 an explicit gating precondition: only call after the human explicitly confirms they want the draft. That is clear when-to-use guidance, but no when-not or named alternative (e.g. reading or promoting an existing draft) is offered.

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