free-blueprints
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_blueprintsA | List available free AI agent blueprints. Returns catalog of pre-built blueprints for common business processes. No signup or API key required. |
| get_blueprintA | Download a free AI agent blueprint by ID. Returns a JSON manifest with all files (SKILL.md, reference docs, implementation guide) ready to write to disk. Same format as the paid Agent Blueprint export. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: listing available blueprints versus downloading a specific blueprint by ID. There is no overlap or ambiguity, as one provides an overview and the other retrieves a detailed artifact.
Both tool names follow a consistent verb_noun pattern: 'list_blueprints' and 'get_blueprint'. This makes the API predictable and easy to reason about.
With only two tools, the surface is minimal but aligns with a read-only catalog service. It borders on thin, but the scope is narrow—listing and retrieving blueprints—so the count is acceptable though not rich.
The lifecycle for a catalog is complete: list and get cover discovery and retrieval. There's no need for update/delete since blueprints are static free resources. Minor gaps like search or filter are absent, but the core workflow is fully supported.