Skip to main content
Glama
moinsen-dev

MCP Package Hero

by moinsen-dev

create_llms_txt

Generates a standardized llms.txt file by scanning your project directory for documentation files and producing structured markdown.

Instructions

Generate an llms.txt file for your project.

Creates a standardized llms.txt file by scanning your project directory for documentation files and generating structured markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionsNoSpecific sections to include (optional, e.g., ["documentation", "examples", "api"]) Available sections: documentation, examples, api, guides, configuration
descriptionYesBrief project description (will appear in blockquote)
project_nameYesName of your project
scan_directoryNoDirectory to scan for documentation (default: current directory).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description only mentions scanning and generating, but does not disclose important behavioral traits like whether it overwrites an existing file, file permissions needed, or error conditions.

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 is concise with two sentences, front-loading the core purpose. However, it could be slightly more structured to separate usage from behavior.

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 tool's low complexity and the presence of an output schema, the description covers the basic functionality but omits details like file location or overwrite behavior, leaving some gaps.

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 coverage is 100% and the description does not add extra parameter context. Baseline 3 applies as the schema adequately describes the 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 generates an llms.txt file by scanning the project directory, with a specific verb and resource. It is easily distinguishable from siblings like get_llms_txt or rate_package.

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?

No guidance on when to use this tool vs. alternatives (e.g., get_llms_txt). It does not provide context such as prerequisites or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/moinsen-dev/mcp-package-hero'

If you have feedback or need assistance with the MCP directory API, please join our Discord server