Skip to main content
Glama
leanzero-srl

MCP Document Processor

Official
by leanzero-srl

dna

Define and update default header, footer, and style presets that auto-apply to every document creation call.

Instructions

Manage the project's Document DNA — header/footer/style defaults that auto-apply to every create-doc call. Actions: 'init' (one-time setup with companyName/header/footer/stylePreset), 'get' (current config + project profile), 'evolve' (analyze usage trends; with apply:true, MUTATES dna config and may auto-create blueprints — irreversible without manual cleanup), 'save-memory'/'delete-memory' (project-wide preferences keyed by string).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key (save-memory: optional, auto-generated; delete-memory: required).
applyNoevolve only: when true, AUTO-MUTATES the dna config based on top suggestion. Off by default — review suggestions first.
actionYesDNA action.
memoryNosave-memory only: a short preference statement (e.g. 'Always use 1-inch margins for contracts').
thresholdNoevolve only: minimum documents before suggesting a mutation (default 5).
footerTextNoDefault footer text (init only). Use {current}/{total} for page numbers.
headerTextNoDefault header text (init only).
companyNameNoCompany name (init only) — used as default header text.
stylePresetNoStyle preset. 'claude-like' (modern blue-accented professional) is the default for general-purpose docs. 'professional' is the executive serif look. Auto-selected from category if omitted.
footerAlignmentNoDefault footer alignment (init only).
headerAlignmentNoDefault header alignment (init only).
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: 'evolve' with apply:true is irreversible, memory actions are project-wide, and DNA auto-applies to create-doc calls. No contradictions noted.

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 a single paragraph but well-organized by actions using semicolons. It is concise with no filler, though a bullet list could improve scannability. All sentences contribute value.

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?

Covers actions and warnings adequately for 11 params and no output schema. Missing details: init idempotency, return format for get/evolve. But remains largely complete for practical use.

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?

Schema coverage is 100%, so baseline is 3. The description adds useful context beyond schema: e.g., 'save-memory: optional, auto-generated' and 'evolve only: when true, AUTO-MUTATES'. This enhances understandability.

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 manages 'Document DNA' (header/footer/style defaults) and lists specific actions: init, get, evolve, save-memory, delete-memory. It differentiates from sibling tools like edit-pptx or create-doc by focusing on reusable defaults.

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?

Each action is explained with context: 'init' for one-time setup, 'evolve' for analyzing trends with a warning about apply:true being destructive. It does not explicitly list when not to use the tool, but the action-based structure provides clear guidance.

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/leanzero-srl/leanzero-mcp-doc-processor'

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