Skavio USDC Payment Verification & Proof MCP

Document ocr

document_ocr

Idempotent

Apply optical character recognition to a scanned document supplied as base64 and return searchable extracted text. Use when the document lacks a usable text layer; use pdf_to_text for selectable PDF text and invoice_extract for invoice fields. This is a separately authenticated company Agent Tools relay; requires a valid Bearer API key, an enabled backend operation and an accepted payment mode. x402 returns a workload-specific quote and prepaid consumes shared company credits. Retry with the SAME idempotency_key and inputs to recover, not a new job. Admission is not delivery: poll skavio_agent_job_status, retrieve through skavio_agent_job_result, and verify SHA256. No anonymous execution.

Input Schema

Name	Required	Description	Default
`arguments`	Yes	Tool-specific structured input object. Supply the required named fields described by its JSON Schema; source bytes must respect encoded size limits. Never include wallet private keys, passwords or API tokens.
`payment_mode`	No	x402 returns a workload-specific quote; prepaid spends your existing shared company credits. No anonymous execution.	x402
`idempotency_key`	Yes	Stable job key; retry exactly the same inputs and payment mode with this key to recover safely.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / arguments / description

Added value: +"Tool-specific structured input object. Supply the required named fields described by its JSON Schema; source bytes must respect encoded size limits. Never include wallet private keys, passwords or API tokens."

Changed9 schema fields changedOct 17, 2026

changedInput schema / properties / arguments / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / arguments / properties

Added value: +{
+  "data_base64": {
+    "description": "Source document or audio bytes in base64, at most 3,000,000 encoded characters.",
+    "maxLength": 3000000,
+    "type": "string"
+  },
+  "units": {
+    "description": "Optional legacy count; verified against actual source bytes. Omit it for automatic measurement.",
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  }
+}

addedInput schema / properties / arguments / required
```
Added value: +[
+  "data_base64"
+]
```
removedInput schema / properties / arguments / title
```
Removed value: -"Arguments"
```

addedInput schema / properties / idempotency_key / description

Added value: +"Stable job key; retry exactly the same inputs and payment mode with this key to recover safely."

addedInput schema / properties / idempotency_key / maxLength
```
Added value: +128
```
addedInput schema / properties / idempotency_key / minLength
```
Added value: +8
```
addedInput schema / properties / idempotency_key / pattern
```
Added value: +"^[A-Za-z0-9_.:-]{8,128}$"
```

addedInput schema / properties / payment_mode / description

Added value: +"x402 returns a workload-specific quote; prepaid spends your existing shared company credits. No anonymous execution."

AddedOct 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses the full operational contract: separate Bearer auth, backend operation enablement, payment-mode tradeoffs (x402 quote vs prepaid credits), idempotent retry semantics, and the asynchronous admission/poll/retrieve/verify flow with SHA256 checking. Nothing here contradicts the annotations – readOnlyHint=false, idempotentHint=true and openWorldHint=true all align with a paid, idempotent job submission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the sibling routing come first, and the operational details follow in a tight sequence. It is a bit long, and 'No anonymous execution' duplicates the payment_mode schema description, but every sentence carries real information.

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 paid, asynchronous, authenticated job tool with no output schema, the description covers everything an agent needs: auth, payment modes, idempotent retry, admission vs delivery, polling via skavio_agent_job_status, retrieval via skavio_agent_job_result, and SHA256 verification.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already documents payment_mode, idempotency_key, data_base64 and units in detail. The description largely restates the idempotency and payment semantics rather than adding syntax, size limits or defaults beyond what the schema provides, so it earns the baseline 3.

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?

The description opens with a specific verb and resource ('Apply optical character recognition to a scanned document supplied as base64') and states the output ('searchable extracted text'). It explicitly distinguishes itself from siblings pdf_to_text and invoice_extract by naming the conditions that select each alternative.

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?

It gives explicit when-to-use guidance ('Use when the document lacks a usable text layer') and names two alternatives with their own selection criteria (pdf_to_text for selectable PDF text, invoice_extract for invoice fields). It also documents the authentication and payment prerequisites needed to invoke the tool at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Skavio USDC Payment Verification & Proof MCP tools Inspect

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.

Document ocr

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources