Skip to main content
Glama
Sign In

Skavio PDF, OCR & Document Processing MCP

by io.github.skavio-eu
OverviewDiscussionsAdmin

skavio_billing_plans

Read-onlyIdempotent

Read current recurring company credit subscription offers, including currency, monthly price, included credits and rollover/expiry policy. Use to compare subscriptions; skavio_pricing covers prepaid packs and operation rates, while skavio_estimate quotes a workload. Returns the plans object without subscribing, creating checkout or spending funds. Takes no arguments. Use skavio_billing_portal to obtain the dashboard URL where a company administrator can review billing actions.

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

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

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds meaningful non-obvious guarantees: it returns the plans object without subscribing, creating checkout, or spending funds. It also clarifies that admin-level billing actions live behind the portal tool. It stops short of describing response shape or caching/refresh behavior, so not a 5.

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-loads what is returned, then sibling routing, then the no-side-effects guarantee. Every sentence carries distinct information and nothing is repeated from the schema beyond a helpful restatement of the zero-argument contract.

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 compensates by naming the returned object and its key fields. For a no-argument read tool, an agent has everything needed to select and invoke it correctly, including where to go for related billing tasks.

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 reinforces this with 'Takes no arguments', and the schema mirrors it by requiring an empty object with company/permissions derived from the authenticated connection. Nothing more is needed.

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?

Specific verb and resource: reads current recurring company credit subscription offers, and it enumerates the contents (currency, monthly price, included credits, rollover/expiry). It explicitly distinguishes itself from skavio_pricing and skavio_estimate, so an agent can identify the right tool without opening a 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?

Names the exact use case (compare subscriptions) and routes three adjacent needs to their proper siblings: prepaid packs/operation rates to skavio_pricing, workload quotes to skavio_estimate, and billing actions to skavio_billing_portal. It also states it takes no arguments, removing setup ambiguity.

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