Skip to main content
Glama
fullbleed-engine

Fullbleed PDF Engine

by fullbleed-engine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Create a Fullbleed project

fullbleed_create_project

Create an agent-ready project or document scaffold in an empty workspace directory. Select a template for invoices, statements

Instructions

Create an agent-ready project or document scaffold in an absent or empty workspace directory; returns generated artifacts and next actions. Use this when starting a project, then render its source with fullbleed_render or fullbleed_render_preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
templateNoScaffold to create: init supplies the general agent-ready project; invoice, statement, accessible, and reference select the corresponding document starter.init
target_pathNoDestination directory under the MCP workspace root. Defaults to that root and must be absent or empty; use a new subdirectory in an existing project..

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.5.2
    • addedInput schema / properties / target_path / description
      Added value: +"Destination directory under the MCP workspace root. Defaults to that root and must be absent or empty; use a new subdirectory in an existing project."
    • addedInput schema / properties / template / description
      Added value: +"Scaffold to create: init supplies the general agent-ready project; invoice, statement, accessible, and reference select the corresponding document starter."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the write/non-idempotent profile, and the description adds the key behavioral constraint that the target must be absent or empty plus the fact that artifacts and next actions are returned. It does not say what happens if the directory is non-empty, which is the main 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the first states what is produced, the second gives the trigger and the follow-up tools. No filler and the important scoping constraint is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values, and it still notes that artifacts and next actions come back. Combined with the annotations and complete schema, an agent has everything needed to invoke this correctly.

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%, with the template enum and target_path fully documented in the schema. The description's mention of an 'absent or empty workspace directory' merely restates the target_path constraint rather than adding syntax or format detail.

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?

States a specific verb (create) and resource (agent-ready project or document scaffold), and names the sibling tools that consume the output (fullbleed_render, fullbleed_render_preview), so it is clearly distinguished from the render family.

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

Usage Guidelines4/5

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

Explicitly says when to use it ('when starting a project') and routes to the correct downstream tools. It does not, however, explain the choice between render vs render_preview or when a scaffold is unnecessary, so it stops short of full when/when-not coverage.

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