Skip to main content
Glama

marketplace-skill-creator

Skill creator kit. The complete methodology for building a skill that sells on agent-skill marketplaces: scoping interview, SKILL.md authoring, support files, a real demo run, listing copy, pricing bands and platform floors, and review gates. One call returns the full kit, from idea to upload-ready zip. Price: $15.00 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "marketplace-skill-creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaNoOptional idea that seeds the scoping step, e.g. turn a meeting-notes routine into a skill.

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?

With no annotations, the description carries the full burden and does well on the highest-risk behavior: it discloses a $15.00 per-call charge in USDC on Base mainnet via x402 and that an unpaid call returns HTTP 402 with machine-readable payment terms — a critical, non-obvious interaction detail. It stops short of stating how the kit is delivered (single text blob vs. downloadable zip), whether repeated calls re-charge, or any rate limits.

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?

Two sentences, front-loaded with the deliverable and then the payment mechanics — the two things an agent must know before calling. The enumerated methodology list is a little dense but each item conveys real scope rather than filler.

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 one-optional-param tool with no annotations and no output schema, the description covers what it produces, its cost, and its failure mode (HTTP 402). Remaining gaps — the concrete return shape and behavior when 'idea' is absent — are minor but not fully negligible.

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 single optional 'idea' parameter is documented at 100% schema coverage, so the schema already explains its purpose and gives an example. The description adds only indirect context ('scoping interview', 'from idea to upload-ready zip') and never says what happens if 'idea' is omitted. Baseline 3 applies when the schema does the work.

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 concrete deliverable — a complete methodology kit for building a sellable agent skill, covering scoping, SKILL.md authoring, support files, demo run, listing copy, pricing and review gates. It is clear what the agent gets back ('from idea to upload-ready zip'), though it never uses an explicit action verb and does not reference any sibling (the listed siblings are unrelated utilities, so differentiation is largely moot).

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?

Usage is implied rather than stated: an agent can infer this is the tool for producing a marketable skill package, but there is no explicit when-to-use or when-not, and no named alternative for adjacent needs (e.g. if you only want listing copy or only pricing guidance). Guidance stops at implication.

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