Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_capabilities

Read-onlyIdempotent

Discover the Processing API operation names, file/media limits, storage features and supported workflow capabilities before choosing a workload. Returns a capabilities object; API capabilities can be broader than this MCP connection permits. Use skavio_paid_catalog for MCP operation aliases and current tenant eligibility, skavio_pricing for tariffs, then skavio_estimate for an uploaded workload. Uses the authenticated company connection; takes no arguments and starts no processing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "skavio_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"No arguments. Send an empty object; company and permissions come from the authenticated connection."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the description only needs to add context — and it does: no arguments, no processing started, authenticated company connection, and the important caveat that reported API capabilities may exceed what this MCP connection permits. It stops short of describing the shape or size of the returned capabilities object, which matters since there is no output schema.

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?

Three sentences, front-loaded with what is discovered, then routing, then the caveat about scope and side effects. Every clause carries routing or behavioral information; nothing is redundant filler.

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 no parameters, no output schema, and annotations covering the safety profile, the description supplies what an agent needs to decide to call it and what to expect broadly. The only gap is that the contents of the returned capabilities object are only alluded to, which is a minor omission given the lack of an output schema.

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?

Zero-parameter tool, so baseline is 4. The description reinforces this ('takes no arguments') and explains where identity and permissions come from — the authenticated company connection — matching the schema note rather than adding new syntax.

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 ('Discover') plus concrete resources (operation names, file/media limits, storage features, workflow capabilities) and explicitly positions itself as a pre-workload step. Sibling tools are named with their distinct roles, so an agent can separate this discovery call from catalog, pricing, and estimation calls without opening any 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 ordering: call this first, then skavio_paid_catalog for MCP aliases/tenant eligibility, skavio_pricing for tariffs, and skavio_estimate for an uploaded workload. 'Before choosing a workload' is a clear trigger condition, and the alternative routing is unambiguous.

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 toolsInspect
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