Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_list_jobs

Read-onlyIdempotent

List recent Processing API jobs owned by the authenticated company, returning a jobs array with each job's id, operation, status, estimated/charged credits and result metadata. Takes no filters or pagination arguments; the response is bounded to at most200 records. Use to discover a job ID or review recent activity; use skavio_get_job to poll one known job and skavio_download_result to fetch its completed output. No work is submitted and no additional processing charge is created.

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_list_jobs"
  }
}

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 cover the safety profile (readOnly, idempotent, non-destructive), and the description adds value on top: the response is capped at 200 records with no pagination arguments, and that no work is submitted and no processing charge is created. The only gap is whether the 200-record cap truncates silently or errors, and there is no guidance on reaching older jobs.

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?

Three sentences, front-loaded with the resource and scope, then return shape, then routing and cost reassurance — every sentence earns its place. Minor blemish: the typo 'at most200' and a dense second sentence packing limits and field list together.

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?

There is no output schema, but the description compensates by enumerating the return fields and the record cap. Combined with the disclosed no-argument design and explicit sibling routing, an agent has everything needed to call it correctly.

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?

With zero parameters the baseline is 4, and the description correctly reinforces that there are no filters or pagination arguments and that company/permissions derive from the authenticated connection. Nothing further is needed since the schema is fully documented.

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 ('List recent Processing API jobs owned by the authenticated company') and enumerates the returned fields (id, operation, status, credits, result metadata). It is clearly distinguishable from mutation siblings like skavio_submit_job and from single-job readers like skavio_get_job.

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?

Explicitly names the two use cases ('discover a job ID or review recent activity') and routes to the correct alternatives: skavio_get_job for polling one known job and skavio_download_result for fetching output. The condition selecting each sibling is stated, not implied.

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