Skip to main content
Glama

pdf_attachments

Inspect, extract, or embed file attachments in PDF portfolios. Read or add embedded files using a PDF input and JSON output.

Instructions

PDF Portfolio Attachments: Inspect, extract, or embed file attachments into PDF portfolios. [Input: .pdf | Output: .json]

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
actionNo
outputYes
file_nameNo
descriptionNo
file_data_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. The '[Input: .pdf | Output: .json]' tag conveys format but says nothing about whether embedding mutates the input PDF, whether existing attachments are overwritten, how binary data is handled, or what happens on failure. For a tool that can write attachments into a document, this is a significant gap.

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?

Compact and front-loaded: the resource label comes first, then the actions, then a bracketed I/O summary. No filler sentences. It is under-specified rather than verbose, and nothing in the text is wasted.

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

Completeness2/5

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

For a six-parameter tool with no annotations, no output schema, and a mutating embed mode, the description is far too thin. It omits the action vocabulary and the semantics of the base64 file payload, which are exactly the details an agent needs to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across six parameters, and the description only indirectly glosses 'input' (.pdf) and 'output' (.json). The 'action', 'file_name', 'description', and 'file_data_base64' parameters — the ones that actually determine behavior in embed mode — are entirely undocumented anywhere, leaving no meaning beyond the raw types.

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?

Names a specific resource (PDF Portfolio attachments) and three concrete verbs: inspect, extract, embed. This clearly distinguishes it from generic PDF converters in the sibling list. However, it does not name which sibling to use for related work (e.g., pdf_extract_patterns), so the differentiation is implicit rather than stated.

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?

The description lists three possible actions but gives no criteria for choosing among them and does not map them to the 'action' parameter. An agent has no guidance on when to inspect versus extract versus embed, nor on prerequisites such as whether the PDF must already be a portfolio.

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