Skip to main content
Glama
lanxiukai

mcp-tools Format Conversion

by lanxiukai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

inspect_pdf_links

Reports Markdown/HTML link references before PDF conversion without writing files, showing local sources, PDF candidates, and evidence so ambiguous mappings can be reviewed.

Instructions

Inspect Markdown/HTML references before PDF conversion, without writing files.

Reports local source paths, source existence, actual PDF candidates, nearby
PDFs and selection evidence. A unique same-stem PDF or recorded source can
be selected automatically; variants and competing sources need review.
For differently named legacy PDFs, inspect nearby files and project output
conventions; the tool cannot infer arbitrary correspondence from a name.
Supply pdf_targets mapping source filenames to actual PDF filenames, or
null to retain the source (e.g. README.md without a PDF). Relative mapping
paths resolve from file_path's directory. A target's .pdf-links.json can
persist a reviewed mapping, relative to that manifest's directory.
Non-Markdown/HTML targets such as .py files retain their original paths.
PDF chapter fragments are verified against the actual PDF. Ambiguous or
missing chapters require resolve_pdf_destination and a pdf_destinations
mapping from the original href to the chosen verified fragment.

Input Schema

NameRequiredDescriptionDefault
file_pathYes
pdf_targetsNo
pdf_destinationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 burden and succeeds in disclosing that it writes no files, explains automatic selection logic, highlights that variants require review, and notes it cannot infer arbitrary name correspondence. Minor ambiguity around whether .pdf-links.json is written by the tool slightly reduces clarity.

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?

The description is front-loaded with purpose and every sentence adds useful information, but it is dense and could be more scannable (e.g., bullet points). For a tool with this complexity, the length is justified, though it could be tightened.

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?

Given no annotations, no output schema, and 0% schema coverage, the description is remarkably complete: it covers purpose, usage, parameter semantics, selection behavior, limitations, and a summary of reported outputs. It stops short of detailing exact output structure, but provides enough for an agent to act correctly.

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 description coverage is 0%, so the description must compensate. It clearly explains pdf_targets (mapping source filenames to actual PDFs or null) and pdf_destinations (mapping original hrefs to verified fragments), including path resolution rules. Only file_path is left to obvious inference.

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 opens with a specific verb and resource: 'Inspect Markdown/HTML references before PDF conversion, without writing files.' It clearly distinguishes the tool from conversion siblings like markdown_to_pdf by emphasizing pre-conversion inspection and read-only behavior.

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?

It states the tool should be used 'before PDF conversion' and explicitly names resolve_pdf_destination as the alternative for ambiguous or missing chapters. It also gives guidance on when the tool cannot infer arbitrary correspondences. However, it does not explicitly exclude other scenarios or sibling tools.

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