Skip to main content
Glama
Sign In
boltwork-mcp

boltwork-mcp

by Squidboy30
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

compare_documents

Compare two PDFs to identify additions, removals, and modifications in a structured diff. Use for contract versions, policy updates, or paper revisions.

Instructions

Compare two PDF documents and return a structured diff. Identifies additions, removals, modifications, and overall similarity. Costs 500 sats via Lightning. Use for: contract versions, policy updates, paper revisions.

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_a": "<url_a>",
      "url_b": "<url_b>"
    },
    "name": "compare_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_aYesURL of the first PDF (original)
url_bYesURL of the second PDF (revised)
max_pagesNoMax pages per document (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.22

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses a key behavioral detail: 'Costs 500 sats via Lightning.' This goes beyond the schema. It does not cover auth needs or error handling, but the cost disclosure is valuable.

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?

The description is very concise: two sentences plus a use-case line. Every sentence adds value, and the main action is front-loaded. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 3 parameters and no output schema. The description explains the purpose and use cases but omits details about return format, error conditions, or limitations (e.g., file size). Adequate but not fully comprehensive.

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%, with each parameter described (url_a, url_b, max_pages). The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 purpose: compare two PDF documents and return a structured diff. It lists specific diff types (additions, removals, modifications, similarity). This distinguishes it from sibling tools like summarise_pdf or analyse_contract.

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?

Explicit use cases are provided: 'contract versions, policy updates, paper revisions.' This gives clear context for when to use the tool. However, no exclusions or alternative tool mentions are included.

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