Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_pricing

Read-onlyIdempotent

Read the live general pricing contract, currency, processing credit rates and prepaid credit packs. Use for tariff/pack questions before files are uploaded; returns the published pricing object, not a workload-specific quote or proof this tenant can process. Use skavio_billing_plans for recurring subscriptions, skavio_paid_catalog for MCP operation aliases and tenant admission status, and skavio_estimate for actual uploaded inputs. Takes no arguments; does not buy credits or reserve 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_pricing"
  }
}

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, and the description adds substantive scope limits beyond them: it returns the published pricing object only, not a tenant-specific quote or admission proof. It also warns it does not purchase credits or reserve funds, which prevents an agent from treating it as a transactional step.

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?

Three sentences, each doing distinct work: what is returned, when to use it plus which siblings to prefer, and the invocation/limits. The resource list and exclusion are front-loaded with no 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?

With no output schema, the description states what the returned object is (published pricing: contract, currency, credit rates, packs) and what it is not, so an agent knows what it will and won't learn. Zero-parameter invocation and auth sourcing are covered.

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. The description's 'takes no arguments' and the schema's note that company and permissions come from the authenticated connection are redundant with each other, adding no meaning beyond the schema, but nothing is left ambiguous.

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 set: reads the live general pricing contract, currency, processing credit rates, and prepaid credit packs. It also names what it is not (not a workload-specific quote, not proof of tenant processing capability), which separates it cleanly from estimate and billing siblings.

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 ('tariff/pack questions before files are uploaded') and routes three alternatives by name: skavio_billing_plans for subscriptions, skavio_paid_catalog for MCP aliases/admission, skavio_estimate for uploaded inputs. Negative guidance ('does not buy credits or reserve funds') closes the most likely misuse.

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