Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_payment_history

Read-onlyIdempotent

Read up to200 company credit-pack and subscription payment records for the current UTC calendar month, newest first. Returns payments with reference, kind, amount_minor, currency, credits, status and creation time, plus truncated and not_a_tax_invoice indicators. Use to inspect recorded purchases; skavio_usage measures processing consumption and skavio_wallet the credit ledger. Trial/promotional credits are not cash receipts. Takes no arguments; does not charge, refund, reconcile a payment provider or issue a tax invoice.

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

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 mark it read-only, idempotent, and non-destructive, but the description adds meaningful behavior: the 200-record cap, current-month restriction, newest-first ordering, a truncation indicator, and the caveat that trial/promotional credits are not cash receipts. It also states that it takes no arguments and performs no billing mutation.

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?

The description is dense but efficient: scope and ordering come first, followed by return fields, then differentiation and exclusions. No sentence is wasted, and the critical routing information is front-loaded.

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 lists the returned fields, including truncation and not_a_tax_invoice indicators, which is important for correctly interpreting results. For a zero-argument read tool, the description covers the key scope, return semantics, and behavioral boundaries.

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?

The tool takes zero parameters, so there is nothing to document, and the description correctly states that no arguments are needed. The schema description also explains that company and permissions come from the authenticated connection, so this dimension is well covered with a baseline score of 4.

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 ... payment records'), plus the exact scope: up to 200 records, current UTC calendar month, newest first. It also names sibling tools with different purposes, so an agent can distinguish it immediately.

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 says to use it to inspect recorded purchases, and routes consumption questions to skavio_usage and credit-ledger questions to skavio_wallet. It also rules out related but distinct actions: charging, refunding, reconciling with a payment provider, or issuing a tax invoice.

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