Skip to main content
Glama

PDF в ч/б

grayscale_pdf

Переводит PDF в оттенки серого (ч/б) — для печати и требований «только ч/б». Текст остаётся текстом. file_url: публичный URL 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_url": "<file_url>"
    },
    "name": "grayscale_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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. The description adds one genuine behavioral fact — 'Текст остаётся текстом' (text is not rasterized) — which matters for output quality, but it says nothing about how the converted file is returned, whether images are degraded, or any limits on file size.

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 sentences, front-loaded with the action and followed by the use case, with no filler. The parameter note is appended inline rather than separated, which is slightly less scannable but costs nothing in length.

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?

For a one-parameter conversion tool with full annotation coverage and an output schema, the description covers what it does, why to use it, the key output trait, and the only parameter. Remaining gaps (return format, file handling) are covered by the output schema and annotations.

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 description coverage is 0% and the schema declares file_url as a bare string, so the description must compensate. It does: 'file_url: публичный URL PDF-файла' tells the agent the value must be a public URL pointing at a PDF, which is real added meaning over the schema.

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?

The description names a specific verb and resource ('Переводит PDF в оттенки серого') and adds the purpose ('для печати и требований «только ч/б»'), which clearly separates it from adjacent siblings like compress_pdf or flatten_pdf. It stops short of explicitly naming those alternatives, so sibling differentiation is implied 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 Guidelines3/5

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

The use case is stated (printing, strict black-and-white requirements), which implies when to reach for this tool. There is no explicit when-not guidance and no mention of the nearest alternative tools (compress_pdf, flatten_pdf), so the agent must infer the boundary.

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.