Skip to main content
Glama

Preview the signing page or email

render_preview
Read-onlyIdempotent

Render markdown exactly as a recipient will see it: the signing page (default) or the signature-request email. Returns HTML you can show your human, plus validation results. Free, no account needed. Once the document is saved as a draft, prefer its preview_url, which your human can open in a browser and use to compare styles.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "markdown": "<markdown>"
    },
    "name": "render_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoWhich view to render. Defaults to signing_page.
styleNoOverrides any <!-- md2sign:style=... --> directive.
messageNoOptional note from the sender shown in the email.
markdownYesThe full markdown contract.
sender_nameNoSender name to show (preview only).
company_nameNoSender company to show (preview only).
sender_emailNoSender email to show (preview only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description still adds real context beyond them: the output is HTML plus validation results, no account is required, and the draft/preview_url handoff. It does not discuss markdown size limits, error behavior, or whether validation failures suppress rendering.

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?

Three tight sentences, front-loaded with what is rendered and what is returned, followed by cost/access and the preview_url alternative. No filler or restatement of the title.

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?

With no output schema, the description correctly compensates by naming the return payload (HTML plus validation results). For a seven-parameter but read-only render tool that is nearly sufficient; a brief note on the shape of the validation results or when rendering fails would close the remaining gap.

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%, so all seven parameters, including both enums and the default, are already documented in the schema. The description confirms the default view but adds no new meaning for style, message, or the sender_* preview-only fields. Baseline 3 is correct when the schema carries the parameter burden.

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 concrete verb (render) and resource (markdown as recipient sees it) and enumerates the two output variants: signing page (default) or signature-request email. It also names the return artifact (HTML plus validation results), so an agent knows exactly what it gets back, differentiating it from validate_markdown and create_draft.

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?

Gives an explicit default (signing_page), an explicit exclusions/alternative rule (once the document is saved as a draft, prefer its preview_url), and a constraint context (free, no account needed). This is when-to-use plus when-to-use-something-else, which is the top bar.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.