Skavio PDF, OCR & Document Processing MCP

skavio_upload

Idempotent

Upload one regular source file already staged by the operator in this adapter's configured input directory. filename is a basename, never an arbitrary path or URL; symlinks are rejected and the configured file-size limit applies. Use skavio_upload_bytes for inline content up to48KiB when no operator-staged file exists. A stable idempotency_key plus identical filename/content replays the stored upload response; changed content conflicts and uncertain uploads require operator reconciliation. Returns uploads with id, kind, size/pages/duration for skavio_estimate. Creates tenant-owned storage, not a processing job; storage quotas apply.

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": {
      "filename": "<filename>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "skavio_upload"
  }
}

Input Schema

Name	Required	Description	Default
`filename`	Yes	Source basename including extension, for example invoice.pdf. No directory separators or URLs; begins with a letter/digit and may contain letters, digits, spaces, underscore, dot or hyphen. For skavio_upload it must already exist in the configured input directory.
`idempotency_key`	Yes	Caller-selected stable identifier8-128 characters (letters, digits, underscore, dot, colon or hyphen) for exactly one upload or job intent. Reuse the same key with identical arguments after a retry; use a different key only for a genuinely new intent, never to bypass an uncertain outcome.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026

addedInput schema / description

Added value: +"Arguments for skavio_upload. Company and permissions come from the authenticated connection."

addedInput schema / properties / filename / description

Added value: +"Source basename including extension, for example invoice.pdf. No directory separators or URLs; begins with a letter/digit and may contain letters, digits, spaces, underscore, dot or hyphen. For skavio_upload it must already exist in the configured input directory."

addedInput schema / properties / idempotency_key / description

Added value: +"Caller-selected stable identifier8-128 characters (letters, digits, underscore, dot, colon or hyphen) for exactly one upload or job intent. Reuse the same key with identical arguments after a retry; use a different key only for a genuinely new intent, never to bypass an uncertain outcome."

First observedOct 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses symlink rejection, the file-size limit, the exact idempotency replay/conflict semantics (identical key+content replays, changed content conflicts, uncertain uploads need supervisor reconciliation), and that it creates tenant-owned storage subject to quotas rather than a processing job. None of that is derivable from readOnlyHint/idempotentHint/destructiveHint alone.

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?

Front-loaded with the primary action and enforced constraints, and every sentence carries information. It is a single dense block, though, and minor typos ('up to48KiB', '8-128') plus the interleaving of alternative guidance mid-paragraph slightly hurt scanability.

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

Completeness5/5

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

With no output schema, the description still explains the return shape (id, kind, size/pages/duration feeding skavio_estimate) and covers the lifecycle facts an agent needs: idempotent retry behavior, conflict handling, quota implications, and that no job is created (so skavio_submit_job is a separate step).

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 100%, so the baseline is 3, but the description adds a behavioral layer the schema lacks: it ties idempotency_key to content-drift conflicts and operator reconciliation, and reinforces that filename is a basename only. It does not add format/syntax detail beyond the schema, which is why it stops short of 5.

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?

States a specific verb and resource ('Upload one regular source file') plus the critical scope constraint that the file must already be staged by the operator in the configured input directory. It explicitly distinguishes itself from the sibling skavio_upload_bytes, so an agent can choose between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit alternative with a condition: use skavio_upload_bytes for inline content up to 48KiB when no operator-staged file exists. It also states the preconditions (basename only, no paths/URLs, symlinks rejected, size limit applies) that determine whether the tool can be used at all.

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

All Skavio PDF, OCR & Document Processing MCP 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.