Skip to main content
Glama
Sign In
Documentation MCP Server

Documentation MCP Server

by ThaLoc0one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

docs_generate_sales_docs

Analyze your PHP project to generate professional sales-ready documentation for marketplaces. Produces comprehensive Markdown files (README, API reference, installation, configuration, examples, FAQ, changelog) with optional PDF export.

Instructions

Generate professional sales-ready documentation for CodeCanyon, ThemeForest, and other marketplaces. Creates comprehensive Markdown documentation (README, Installation, API Reference, Configuration, Examples, FAQ, Changelog) with optional PDF export.

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": {
      "projectPath": "<projectPath>",
      "productName": "<productName>",
      "author": "<author>",
      "description": "<description>"
    },
    "name": "docs_generate_sales_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to the PHP project directory to analyze
outputDirNoOutput directory for documentation files (default: ./sales-docs)
productNameYesProduct name for marketplace listing (e.g., 'Advanced User Management System')
productVersionNoProduct version (default: '1.0.0')
authorYesAuthor or company name (e.g., 'Your Company')
descriptionYesProduct description for the README (e.g., 'A comprehensive user management system with advanced features...')
priceNoProduct price (optional, e.g., '$49' or '€39')
demoUrlNoLive demo URL (optional)
supportEmailNoSupport email address (optional)
featuresNoList of key product features (e.g., ['User authentication', 'Role-based access', 'API support'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that it creates Markdown files and optionally exports PDF, and lists the sections. However, it does not clarify whether it modifies existing files, requires specific permissions, or if analyzing the project path is read-only. This is adequate but lacks deeper behavioral context.

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?

The description consists of two concise, front-loaded sentences. The first captures the main purpose, the second details the output. It is efficient though could be slightly more structured (e.g., bullet points) for clarity.

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?

Given the complexity (10 parameters, no output schema), the description covers the core functionality but omits details about return values, failure cases, or prerequisites (e.g., that the project must be PHP). It is adequate for a basic understanding but not fully complete.

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%, so the baseline is 3. The description does not add extra meaning beyond what the schema already provides for each parameter. It lists the generated sections but does not link them to specific parameters.

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?

The description clearly states the tool's purpose: generating professional sales-ready documentation for specific marketplaces like CodeCanyon and ThemeForest. It lists the sections created (README, Installation, etc.), distinguishing it from sibling tools like docs_generate_api or docs_generate_structure.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool versus its siblings. It mentions marketplaces but does not explain that this is for sales documentation while other tools are for API docs or general project analysis. No alternatives or exclusions are mentioned.

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

Deploy Server

Other Tools