Skip to main content
Glama
Sign In
Agent.ai MCP Server

Agent.ai MCP Server

by OnStartups
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

file_converter_merge_action

Convert and merge multiple files into a single PDF. Non-PDF files are automatically converted before merging.

Instructions

Combine multiple files into a single PDF. Non-PDF files are automatically converted to PDF before merging.

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_file_urls": "<input_file_urls>",
      "output_variable_name": "<output_variable_name>"
    },
    "name": "file_converter_merge_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_file_urlsYesOne URL per line. S3 or public URLs of files to merge.
output_variable_nameYesVariable name for the result.merged_file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses automatic conversion to PDF but lacks details on file size limits, supported formats, or output storage behavior.

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 a single sentence with no extraneous words. Every part contributes to understanding the tool's function.

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?

The description covers the core function and auto-conversion. Given no output schema and 2 simple parameters, it is mostly complete, though it could mention output variable behavior.

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%, so baseline 3. The description adds no additional meaning beyond the schema; it does not elaborate on URL format or output variable.

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 combines multiple files into a single PDF and automatically converts non-PDF files. This distinguishes it from sibling tools like split or convert.

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

Usage Guidelines3/5

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

The description implies usage for merging files into a PDF but does not explicitly state when to use or avoid this tool, nor does it compare to alternatives among siblings.

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