Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_adapter_usage

Read-onlyIdempotent

Read this authenticated company MCP adapter's lifetime accounting: charged credits, reserved credits, configured limit and available credits. Available equals max(0, limit minus charged minus reserved); uncertain submissions remain reserved until supported reconciliation. Takes no arguments; the connection selects the company. Use when diagnosing adapter_budget_exceeded, skavio_usage for current UTC-month company totals, skavio_budgets for monthly ceilings, or skavio_wallet for the authoritative upstream wallet. Reading this does not clear reservations or replenish funds.

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_adapter_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 already declare readOnly/idempotent/non-destructive, yet the description adds genuine behavior: the exact availability formula, that uncertain submissions stay reserved until supported reconciliation, and that reads are side-effect-free with respect to reservations and funds. Nothing contradicts the annotations.

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?

Front-loaded with what is read, then the formula, then the reservation caveat, then sibling routing. Dense but every clause carries distinct information with zero filler.

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?

No output schema and no params, so the description must carry semantics, side-effect expectations, and disambiguation — and it does all three, including the reservation lifecycle edge case an agent would otherwise misread.

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 sets a baseline of 4; the description goes slightly beyond by explaining that the connection supplies company and permissions, which clarifies why no arguments exist. There is no additional argument-level detail to add.

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 ('Read ... lifetime accounting') and enumerates exactly what is returned: charged credits, reserved credits, configured limit, available credits. This is clearly distinguished from skavio_usage (current month), skavio_budgets (ceilings), and skavio_wallet (upstream wallet).

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 trigger ('Use when diagnosing adapter_budget_exceeded') and routes to three named alternatives with the condition each covers. The closing sentence also excludes a false expectation ('does not clear reservations or replenish funds').

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