Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_wallet

Read-onlyIdempotent

Read the authenticated company's authoritative prepaid credit balance, reserved credits and recent credit-ledger entries. Takes no arguments: the company comes from the connection, not caller input. Use before submitting work to check funds; this does not top up or start a payment. Use skavio_budgets for monthly company/key ceilings, skavio_adapter_usage for this MCP adapter's lifetime ceiling, and skavio_payment_history for cash payment records. Credit-ledger entries are not proof of a card or blockchain payment.

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

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

A5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the authorization model ('the company comes from the connection, not caller input') and two important caveats: it cannot mutate funds, and credit-ledger entries are not proof of a card or blockchain payment.

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 short sentences, front-loaded with the payload description, followed by usage routing and caveats. No filler or restatement of the title.

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?

For a read-only, zero-arg tool with no output schema, the description names exactly what is returned (balance, reserved credits, ledger entries) and pre-empts the most likely misuses (topping up, treating ledger entries as payment proof). Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero-parameter tool, so the baseline is already high; the description still adds meaning by explaining why there are no arguments and where the company scope is derived from, preventing an agent from attempting to pass a filter.

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 ... authoritative prepaid credit balance, reserved credits and recent credit-ledger entries') and explicitly distinguishes itself from skavio_budgets, skavio_adapter_usage and skavio_payment_history, which occupy adjacent financial-reporting space.

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 trigger ('Use before submitting work to check funds'), an explicit exclusion ('this does not top up or start a payment'), and names three alternatives with the condition each covers. Nothing is left to inference.

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