Skip to main content
Glama

Excel в PDF

xlsx_to_pdf

Конвертирует таблицу Excel (.xlsx/.xls) в PDF. file_url: публичный URL XLSX-файла.

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_url": "<file_url>"
    },
    "name": "xlsx_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond them: the file must be reachable at a *public* URL, which implies server-side fetching and will fail on private/intranet links. It says nothing about formatting/stylesheet fidelity, multi-sheet handling, or what happens on fetch failure.

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 short lines, the conversion statement front-loaded ahead of the parameter note, with zero filler. It is arguably slightly under-specified rather than over-written, but nothing is wasted.

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?

With only one parameter, an output schema in place (return values need not be described) and annotations covering the safety profile, the remaining burden on the description is small. Purpose, accepted input formats and the public-URL requirement are all present; only edge-case behavior (large files, formatting loss, fetch errors) is absent, which is a minor gap for a simple converter.

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

Parameters4/5

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

Schema coverage is 0% — file_url has a bare "type: string" with no description — so the description must carry the meaning, and it does: it states the parameter is a public URL of an XLSX file, which is the single most important thing to know. It stops short of showing an example URL or accepted hosting patterns, but the essential semantics are supplied.

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?

"Конвертирует таблицу Excel (.xlsx/.xls) в PDF" gives a specific verb (convert), a specific source resource (.xlsx/.xls) and a specific target format (PDF), so the direction is unambiguous. Against siblings like pdf_to_excel or word_to_pdf an agent can instantly tell which one applies, though the description never names an alternative to reinforce that.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites beyond the parameter annotation, and no mention of alternatives (e.g. going via word_to_pdf, or pdf_to_excel for the reverse direction). The only implicit routing signal is that the input must be an Excel file, which the agent infers rather than reads.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.