Skip to main content
Glama

Export the research report (PDF)

inspo_export_pdf

Render a studio-style PDF report of design research, including cover, brief, winning references, notes, liked styles, components, and current page version; save and open it.

Instructions

Render a studio-style PDF report of the research: cover, direction/brief (or taste profile), the winning references of every section with the user's notes, liked styles and components, and the current page version. Saved to .inspo//inspo-report.pdf and opened.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspo_export_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNoOpen the PDF (default true).
sessionNoSession id. Defaults to the most recent session in this project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does real work: it names the exact output path (.inspo/<session>/inspo-report.pdf), states that the file is written AND opened (a visible side effect on the user's machine), and lists what content is snapshotted. It stops short of saying whether an existing report is overwritten or what happens when no session exists.

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 verb and artifact, then a single content inventory with zero filler. The long comma-delimited content list is dense but each item earns its place by telling the agent what the output looks like.

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?

For a two-parameter, zero-required, no-output-schema tool whose only real questions are what it produces, where it lands, and what side effects it has, the description answers all three. Only overwrite/error behavior and the return value are left unstated.

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 coverage is 100%, so both parameters are already documented, and the description adds only indirect meaning ("opened" maps to open=true, "current page version" gestures at the session default). Baseline 3 is appropriate when the schema does the explaining.

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?

Opens with a specific verb and artifact: "Render a studio-style PDF report of the research," then enumerates the exact sections the report contains. No sibling tool produces a PDF report, so an agent can select it without ambiguity.

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

Usage Guidelines3/5

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

Usage is only implied — the wording suggests it is a terminal step that packages research into a document, but it never states when to call it versus e.g. inspo_review or inspo_catalog, nor any prerequisite (login, completed sections). An agent must infer the trigger condition.

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