Skip to main content
Glama
Sign In

Picorn

by io.github.cueqzapper
OverviewDiscussionsAdmin

Picorn Blueprint: compile, review and preview

picorn_blueprint_compile
Read-only

Compile a PBL document you wrote (pbl) or apply #id patch lines to an earlier compile (blueprintId + patch). No model is called: Picorn searches the curated asset libraries, measures text with the real fonts, lays out, reviews and renders. Returns blueprintId, errors/warnings with codes and fixes, the scene report + ASCII wireframe (exact boxes, colours, effects, search hits), the canonical source and an inline preview of every slide. Patches reuse the cached asset searches, so iterate with small patches until errors=0 and the preview is visually finished. blueprintId alone re-sends the current revision (preview and report) without compiling. Set preview:false for an even faster text-only check. A line search q2 generate photo "…" (or generate text for lettering-heavy mockups) creates a NEW picture as ref when the library has nothing fitting; Library first: browse with picorn_search_library (or use search lines in picorn_blueprint_compile), and generate only when the design would benefit massively from a new picture (no fitting hero photo exists). Generation needs a connected Picorn account with credits; it is charged at 1.2 × the fal price (a Krea 2 Turbo picture of about 1 MP costs about 1 ct). Generated pictures are cached in the blueprint, so patches never pay twice.

Input Schema

NameRequiredDescriptionDefault
pblNoFull PBL document starting with "pbl v1". Creates a new blueprintId.
patchNoRepair lines, e.g. "#title size=96 color=primary" or "#n12 delete".
previewNoRender the inline preview. Default true.
blueprintIdNoFrom an earlier compile, together with patch (or alone to see the current revision again).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / blueprintId / description
      Previous value: -"From an earlier compile, together with patch."New value: +"From an earlier compile, together with patch (or alone to see the current revision again)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

With only readOnlyHint/openWorldHint to work from, the description carries the burden well: it says no model is called during compile, that real fonts are measured and asset libraries searched, that patches reuse cached searches, and that generation requires a connected account with credits at 1.2x fal price with per-blueprint caching. These are concrete cost, caching, and side-effect disclosures beyond the annotations.

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 core compile/patch purpose is front-loaded in the first sentence, and subsequent sentences are information-dense rather than padded. It is long and slightly nested around the generation-line syntax, but virtually every sentence carries actionable detail.

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?

For a complex compile/render tool with no output schema, the description enumerates exactly what comes back (blueprintId, coded errors/warnings with fixes, scene report, ASCII wireframe, canonical source, inline preview) and describes the iteration loop to errors=0. Nothing essential is left for the agent to infer.

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 3 is the baseline, but the description adds genuine meaning: it explains the blueprintId+patch interplay, the standalone blueprintId behavior, and the speed tradeoff of preview:false. This goes beyond the terse property descriptions in the schema.

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 states a specific verb and resource — compile a PBL document or apply patch lines to an existing blueprintId — and clearly delineates the two modes of operation. An agent can distinguish this from siblings like picorn_render_svg or the editor_* tools without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit routing rules: use pbl for a new compile, blueprintId+patch to iterate, blueprintId alone to re-fetch the current revision, preview:false for a text-only check. It also names the sibling (picorn_search_library) and states the condition under which generation lines should be used at all ('Library first').

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

All Picorn toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources