drukarnia

get_file_specs

Get print-file preparation requirements for a barwa.pl product (format, color mode, resolution, bleed) plus a link to the how-to-prepare guide. The ai_generation section gives exact pixel dimensions (bleed included, 300 DPI) for AI image generators — pass width_mm/height_mm (trim size in millimeters) to get pixel dimensions for a custom size.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`width_mm`	No
`height_mm`	No
`product_slug`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 31, 2026

addedInput schema / properties / height_mm

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / width_mm

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedJul 16, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It explains what the tool returns and how width_mm/height_mm affect pixel dimensions, but it does not explicitly state that this is a read-only operation, mention authentication prerequisites, or address invalid inputs. This is a partial disclosure.

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?

Two sentences, front-loaded with the primary purpose, and the second sentence adds a specific use case (AI image generation) without redundancy. Every word earns its place.

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 main purpose, a special feature (ai_generation), and parameter behavior. Since an output schema exists, return values need not be detailed. Minor gaps include prerequisites and error conditions, but overall it's sufficient for an AI agent to decide invocation.

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 description coverage is 0%, so the description must compensate. It explains width_mm and height_mm as trim size in millimeters used to compute custom pixel dimensions, which adds value. However, product_slug is not explicitly described, though it is implied by 'barwa.pl product'. Partial compensation.

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 verb 'Get' and the resource 'print-file preparation requirements for a barwa.pl product', specifying format, color mode, resolution, bleed. This distinguishes it from sibling tools like get_quote or list_products.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool — when print-file specs or AI-generator pixel dimensions are needed. It doesn't explicitly exclude alternatives, but the sibling tools have distinct purposes, so the context is sufficient.

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

All drukarnia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?