Skip to main content
Glama
Sign In
publicsofttools-mcp

publicsofttools-mcp

by DrEjazAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

compress_pdf

Reduce PDF file size by compressing it. Accepts base64-encoded input and returns a compressed version with adjustable quality settings.

Instructions

Compress a PDF file to reduce its size. Accepts a base64-encoded PDF, returns a compressed base64 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": {
      "file_base64": "<file_base64>"
    },
    "name": "compress_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_base64YesBase64-encoded PDF file content
qualityNoCompression quality: screen (lowest/smallest), ebook (balanced), printer (high quality), prepress (highest). Default: ebook

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided; description only covers I/O format. Missing details on lossy behavior, size limits, safety, and other traits beyond what is obvious.

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?

Two sentences covering key points. Efficient, though could add brief usage guidance without bloat.

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?

Adequate for a simple tool with two well-described params, but missing behavioral context (lossy, limits) that would help agent. Output schema absent but return type is hinted.

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 has 100% parameter description coverage (file_base64 and quality). Description adds no extra semantic value beyond repeating schema.

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?

Clearly states it compresses PDF files to reduce size, specifying base64 input/output. Distinct from sibling tools like merge_pdfs, split_pdf, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use compression vs alternatives, no when-not-to-use or prerequisites mentioned.

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