Skip to main content
Glama
Sign In
career-mcp

career-mcp

by sindhujaIBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

export_pdf

Render a saved markdown resume or requested cover letter to an ATS-readable PDF using the installed browser; defaults to the active tailored resume and writes HTML if no browser is found.

Instructions

Render a saved markdown document to a PDF that ATS systems can read, using the user's installed Chrome/Edge/Chromium/Brave. Defaults to the active application's tailored resume. Only export a cover letter when the user asks for one. If no browser is found, an HTML file is written instead and the reason is returned — relay it to the user.

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": "export_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNonavy (default: modern sans, navy accents), minimal (monochrome, compact), classic (serif, centered header)
documentNotailored_resume (default), cover_letter, or base_resume (the stored base resume)
page_sizeNoletter (default) or a4
application_slugNoOptional — defaults to the active application. Ignored for base_resume.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does real work: it discloses the browser dependency, the degraded fallback (an HTML file is written instead), and that a reason is returned which the agent must relay. What's missing is where the PDF lands on disk and what a successful return looks like, but the failure path — the riskiest part — is covered.

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 sentences, each earning its place: capability first, default/guardrail second, failure behavior and required follow-up last. The most decision-relevant information is front-loaded and there is no filler.

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 four-parameter, all-optional export tool with no output schema and no annotations, the description covers purpose, defaults, a usage restriction, and the failure mode. Only the success-path artifact (output file location/naming) is left unstated, which is a minor 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 theme, document, page_size and application_slug are already fully documented in the schema. The description only restates two defaults (tailored_resume, active application), adding no syntax or format detail beyond structured data. Baseline 3 applies.

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 ('Render a saved markdown document to a PDF') plus the mechanism (user's installed Chrome/Edge/Chromium/Brave) and the quality goal (ATS-readable). No sibling tool in the list does PDF rendering, so an agent can pick this one unambiguously.

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?

Gives concrete routing context: default to the active application's tailored resume, and an explicit exclusion — only export a cover letter when the user asks. No alternative tool is named, but none of the siblings is a competing exporter, so the guidance is effectively complete.

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