Skip to main content
Glama
Sign In
Typst Web MCP

Typst Web MCP

by caphefalumi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

typst_capture_screenshot

Capture high-resolution PNG screenshots of a Typst project to verify its visual output, either by rendering compiled pages or by capturing the live typst.app editor and preview.

Instructions

Capture high-resolution PNG preview screenshots to verify the visual status of a https://typst.app project (mode='pages' renders compiled PNG pages via Typst; mode='browser' captures the live typst.app web editor & preview pane via Playwright).

Input Schema

NameRequiredDescriptionDefault
ppiNoPixels per inch resolution for rendered PNGs (default: 144)
modeNo'pages' (default) compiles high-DPI PNG pages from synced project files; 'browser' captures the live https://typst.app/project/:id UI
pagesNoPage range to capture, e.g. '1', '1-3', '1,4', or 'all' (default: 'all')
mainFileNoOptional main .typ entry file override
outputDirNoOptional directory path to save the rendered PNG screenshot files
projectIdYesThe Typst project ID
includeBase64NoInclude screenshots as image blocks for direct vision inspection (default: true; set false to return paths and metadata only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • changedInput schema / properties / includeBase64 / description
      Previous value: -"Include base64-encoded PNG data in response for direct vision inspection (default: false)"New value: +"Include screenshots as image blocks for direct vision inspection (default: true; set false to return paths and metadata only)"
  2. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

Since no annotations are provided, the description carries the burden of behavioral transparency. It adds crucial operational details like referencing 'Playwright' for web capture and specifying the output format (PNG previews).

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?

The description is dense but highly efficient, dedicating one sentence to defining the entire tool's function and its modes without unnecessary filler.

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 the lack of an output schema, the description is fully self-contained, explaining the nature of the input and the resulting visual verification output.

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?

The description provides essential context for the function's purpose (visual status verification) which the schema merely implements. It also explains the implication of the 'mode' parameter.

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 goal (capture high-resolution PNG preview screenshots) and precisely defines the two different operational modes ('pages' vs. 'browser'), making it easily distinguishable from standard file read/write tools.

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?

The distinction between the 'pages' mode (compilation) and the 'browser' mode (live capture) effectively guides the agent on when to use the tool for different visual verification tasks.

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