Skip to main content
Glama
lanxiukai

mcp-tools Format Conversion

by lanxiukai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

resolve_pdf_destination

Locate a chapter in a target PDF without writing files by searching named destinations, outline titles, and text lines; returns page, evidence, and candidates.

Instructions

Locate a chapter in the actual target PDF without writing files.

Searches existing named destinations, exact normalized outline titles, then
complete text lines. target is the title, source anchor, or PDF fragment.
Returns status, physical 1-based page, printed page_label, evidence basis,
and candidates. Only a unique match returns a top-level fragment and uri.
For repeated titles, inspect the candidates and use page to narrow the
search or select a candidate's fragment. Never guess printed-page offsets.
For scans without usable text or bookmarks, use OCR to establish the page,
then validate page=N here. Text-line matches require context review.
Use the returned URI for PDF links, or pass pdf_destinations={original_href:
fragment} when converting Markdown/HTML. Recheck after the target changes.

Input Schema

NameRequiredDescriptionDefault
pageNo
targetYes
file_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses the search order, what a unique match returns, how candidates behave, when to use page, privacy-relevant no-write behavior, and caveats around guessing printed-page offsets and text-line evidence.

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 dense but front-loaded, starting with the core purpose and then layering search order, return behavior, and caveats. Every sentence appears useful, though the run-on structure could be made more scannable.

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?

For a tool with no output schema, no annotations, and low schema-description coverage, the description is unusually complete. It explains return fields, unique-match behavior, candidate handling, OCR fallback, URI usage, and rechecking, which is enough for an agent to invoke and interpret it 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 explain parameters itself. It clearly defines target as a title, source anchor, or PDF fragment, and explains page as a search-narrowing or validation input, though file_path is only inferred from context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: locating a chapter in the actual target PDF without writing files. It is clear what the tool does and distinguishes it from file-producing conversion tools, though it does not explicitly name or differentiate itself from siblings like inspect_pdf_links.

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 explains what target may contain and gives concrete operational guidance for repeated titles, OCR fallback, text-line matches, and after-target changes. The usage context is clear, but it stops short of explicitly naming sibling-tool alternatives or exclusions.

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