Skip to main content
Glama

Emboss

by io.github.edwinorange
OverviewDiscussionsAdmin

Create a fillable form from a PDF

create_form

Turn a flat or scanned PDF form into a fillable PDF with detected fields. Upload a PDF (pdf_url: public https link, or pdf_base64) and detect its fields. Returns when detection finishes (usually under two minutes). Give library= from find_form to start from a form Emboss already keeps. Billed as one form creation; the first 5 each month are free. Optional retention: ephemeral or account_default (default: the account's own setting). Ephemeral processing: source and output documents are deleted 60 to 70 minutes after the last activity on a form. Pass dry_run=true to rehearse this call without doing it: nothing is stored, charged or sent, and no AI is used. The answer says whether the real call would succeed or be refused, what it would cost, and what a rehearsal cannot check.

Input Schema

NameRequiredDescriptionDefault
titleNo
dry_runNo
libraryNo
pdf_urlNo
retentionNo
pdf_base64No

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "pdf_url": "https://example.com/forms/building-permit.pdf",
-    "retention": "ephemeral"
-  }
-]New value: +[
+  {
+    "pdf_url": "https://example.com/forms/building-permit.pdf",
+    "retention": "ephemeral"
+  },
+  {
+    "dry_run": true,
+    "pdf_url": "https://example.com/forms/building-permit.pdf",
+    "retention": "ephemeral"
+  }
+]
    • addedInput schema / properties / dry_run
      Added value: +{
+  "default": false,
+  "title": "Dry Run",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "pdf_url": "https://example.com/forms/building-permit.pdf",
+    "retention": "ephemeral"
+  }
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond annotations: blocking behavior with typical latency ('under two minutes'), billing ('one form creation; first 5 each month free'), retention semantics including the 60–70 minute deletion window, and precisely what dry_run does and cannot check. This goes well past readOnlyHint/destructiveHint=false.

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?

Front-loaded with the core action and source options, then billing, retention, and dry_run in a logical order. Slightly dense as one paragraph, and the dry_run explanation repeats part of the retention sentence's cadence, but nearly every sentence carries information.

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?

Given no annotations detail beyond hints, 0% schema coverage, and an existing output schema (so return shape needn't be explained), the description covers source inputs, blocking latency, cost, retention lifecycle, and rehearsal limits. An agent has what it needs to call this correctly and predict side effects.

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 0%, so the description must carry the load, and it explains pdf_url format ('public https link'), pdf_base64, library's origin in find_form, retention's two allowed values and default, and dry_run's effect. It leaves title unexplained and doesn't say the source parameters are mutually exclusive or that one is required.

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 and resource ('Turn a flat or scanned PDF form into a fillable PDF with detected fields') and distinguishes itself from nearby siblings like prepare_form and read_form by describing field detection on upload. An agent can tell what this creates 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 Guidelines4/5

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

Says explicitly when to supply library=<slug> from find_form versus uploading a PDF, and explains what dry_run does. However, it never states what to do when neither pdf_url nor pdf_base64 nor library is present, despite zero required parameters, so the agent has no explicit instruction on the requirement to supply a source.

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

All Emboss 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