Skip to main content
Glama

playbook_mcp_publish

Build and publish an MCP server to the official registry with this guide, including a free demo TOC and excerpt; successful paid calls cost 3 USDC on Base via x402.

Instructions

Playbook: build and publish an MCP server to the official registry. Concise guide from Forge Agent Hub's own publish. ?demo=1 returns the TOC and an excerpt, unpaid. Costs 3 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "playbook_mcp_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/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 so well: it discloses the price (3 USDC on Base), the payment protocol (x402), and exactly what happens without a payment key (a 402 challenge is returned). It doesn't describe the returned content's format or length for a paid call, which is the remaining gap.

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: what it is, the free preview option, then the paid-call terms and failure mode. Information is front-loaded with no filler. The inline '?demo=1' reads slightly like a URL fragment rather than a tool argument, which is a small clarity blemish.

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 zero-parameter, no-output-schema content tool, the definition covers identity, pricing, payment mechanism, and the unpaid failure path. What's missing is a hint about the shape of the returned playbook (steps, markdown, length) so an agent knows what it is buying.

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

Parameters4/5

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

The input schema is empty, so baseline is 4. The description adds the only meaningful invocation detail — the ?demo=1 query flag that switches to the free TOC-plus-excerpt mode — even though that flag isn't represented in the schema.

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 resource ('an MCP server to the official registry') and handy framing ('Concise guide from Forge Agent Hub's own publish'), so an agent understands this returns documentation rather than performing a publish. It doesn't name a specific sibling, but the playbook framing inherently separates it from action tools like openapi_to_mcp.

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 '?demo=1 returns the TOC and an excerpt, unpaid' line gives a practical try-before-pay path, which is useful guidance. However, it never says when to reach for this playbook versus related siblings such as playbook_x402_seller, nor what prerequisite knowledge it assumes.

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