Skip to main content
Glama

Propose a Playground project skill version

playground_project_skill_propose

Submit instructional Markdown for human review in Playground. The proposal is inactive and grants no tools, connections, or billing rights. Returns skill and proposal IDs, version and proposed status.

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": {
      "projectId": "<projectId>",
      "slug": "<slug>",
      "title": "<title>",
      "summary": "<summary>",
      "instructions": "<instructions>",
      "provenance": "<provenance>"
    },
    "name": "playground_project_skill_propose"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesStable short name for the proposed project skill.
titleYesHuman-readable label to display for this item in Playground.
summaryYesBrief explanation of what the proposed skill helps the user accomplish.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
provenanceYesSource information explaining where the proposed skill instructions came from.
instructionsYesInstructions to save for the selected skill or node.
requiredCapabilitiesNoCapability names that must be available to use this proposed skill.

Output Schema

NameRequiredDescriptionDefault
statusYes
skillIdYes
versionYes
proposalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false, openWorld=false), the description adds genuinely useful behavioral facts: the proposal is inactive, grants no tools, connections, or billing rights, and is subject to human review. It also names what is returned (skill and proposal IDs, version, proposed status). It omits the key non-idempotency consequence — that repeated submissions likely create separate proposals rather than updating one.

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 tight sentences with the action front-loaded, followed by the safety/scope caveat and the return value — no filler. The final return-value sentence is mildly redundant given an output schema exists, which keeps it from a 5.

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?

Annotations, a 100%-documented schema, and an output schema carry most of the load, and the description supplies the crucial 'this does not activate anything' framing an agent needs before calling it. What is missing is the lifecycle context: how the proposal is later approved or superseded, and whether re-proposing the same slug creates a new version.

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% across all 7 parameters, including the projectId sourcing hint and the requiredCapabilities enum, so the schema already carries parameter meaning. The description adds nothing parameter-specific (e.g., how instructions length relates to the 12000-char cap, or how requiredCapabilities interacts with the 'grants no tools' claim), so the baseline 3 applies.

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 states a specific verb and resource: 'Submit instructional Markdown for human review in Playground,' which combined with the title makes the created artifact (a skill proposal) unambiguous. It does not explicitly contrast with siblings such as playground_skill_load or playground_memory_propose, so differentiation is inferred rather than stated.

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 mention of 'human review' implies this tool is the path for proposing rather than activating a skill, and the 'inactive' note hints it is a pre-approval step. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites like an existing projectId, and no pointer to the approval flow or the alternative of loading an already-approved skill.

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.