Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_usage

Read-onlyIdempotent

Read the authenticated company's current UTC calendar-month processing usage, attributed by job admission month. Returns month/timezone, charged/reserved/exposure credit totals, job status counts and groups by channel, operation and API key. Takes no arguments and includes company activity beyond this adapter; historical key attribution before platform1.7 is unavailable. Use skavio_adapter_usage for the MCP lifetime ceiling, skavio_wallet for funds available now, or skavio_payment_history for credit purchases. Does not submit work or change budgets.

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

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.9/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/open-world, but the description adds substantive traits the agent could not infer: the window is the current UTC calendar month by admission date, results include company-wide activity beyond this adapter, and per-key attribution is unavailable before platform 1.7. These are real data-scope caveats that prevent misreading of totals.

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?

Four sentences, each doing distinct work: scope, return shape, data caveats, sibling routing. Scope and the return contract are front-loaded, and the closing negation removes the most likely confusion up front.

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 carries the return contract itself and does so by enumerating the returned fields and groupings. Combined with the attribution caveats and sibling routing, an agent has everything needed to call this correctly and interpret the result.

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 parameters, so the baseline is 4. 'Takes no arguments' confirms the empty-object schema and the schema itself explains that identity and permissions come from the authenticated connection; the description adds no further parameter detail, which is appropriate here.

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 — reading the authenticated company's current UTC calendar-month processing usage, attributed by job admission month — and enumerates what is returned (charged/reserved/exposure totals, status counts, groupings by channel, operation, API key). An agent can separate it from skavio_wallet, skavio_adapter_usage and skavio_payment_history 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?

Explicitly routes the agent: use skavio_adapter_usage for the MCP lifetime ceiling, skavio_wallet for funds available now, skavio_payment_history for credit purchases. It also closes the opposite direction with 'Does not submit work or change budgets', leaving no ambiguity about when this tool applies.

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