boltwork-mcp

summarise_pdf

Summarize any PDF from a URL, extracting title, key points, sentiment, topics, and word count. Useful for research papers, reports, and contracts.

Instructions

Summarise a PDF document from a URL. Returns a structured summary including title, key points, sentiment, topics, and word count. Costs 500 sats via Lightning. Use for: research papers, reports, contracts, any PDF.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "summarise_pdf"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	URL of the PDF to summarise
`max_pages`	No	Max pages to process (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.22May 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the cost ('500 sats via Lightning') and the structured output fields, which adds significant transparency. However, it omits details like authentication requirements, error conditions, or whether the PDF must be publicly accessible.

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 with no wasted words. The first sentence states the action and output, the second adds cost, the third lists use cases. Every sentence serves a clear purpose.

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 simple parameters and no output schema, the description adequately covers purpose, output, cost, and usage context. It lacks information on error handling or document size limits, but for a tool of this complexity, it is reasonably complete.

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 the baseline is 3. The description does not add extra meaning to the parameters beyond what the schema provides (url and max_pages). The cost mention is behavioral, not parameter-specific.

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 tool's action ('Summarise a PDF document from a URL') and the output structure ('title, key points, sentiment, topics, and word count'). It distinguishes from siblings like summarise_webpage (which works on webpages) and analyse_contract (likely contract-specific) by specifying usage for 'research papers, reports, contracts, any PDF'.

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 description explicitly lists use cases ('research papers, reports, contracts, any PDF'), providing clear context for when to use. However, it does not explicitly state when not to use or offer alternatives beyond what's implied by sibling tool names.

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

Deploy Server