Skavio USDC Payment Verification & Proof MCP

Pdf split

pdf_split

Idempotent

Select one-based page numbers from an uploaded PDF and return a new document containing those pages. Use to extract pages; use pdf_merge to concatenate two to five whole PDFs or pdf_to_text for reading text. 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"
+  },
+  "pages": {
+    "description": "One-based PDF pages to keep, at most 100.",
+    "items": {
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "maxItems": 100,
+    "minItems": 1,
+    "type": "array"
+  },
+  "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",
+  "pages"
+]
```
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.7/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=true, openWorld=true), and the description adds substantial non-redundant context: authentication requirements, payment modes, idempotency retry semantics ('SAME idempotency_key and inputs... not a new job'), and the admission-is-not-delivery polling/verification flow. Nothing here contradicts the annotations.

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?

Front-loaded with the core action and sibling disambiguation, which is the right order. The middle section on relay authentication and x402/prepaid payment is boilerplate-heavy and could be tightened, but every clause is actionable information an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an async, authenticated, paid job-launching tool with no output schema, the description supplies the full lifecycle: submit, poll skavio_agent_job_status, retrieve via skavio_agent_job_result, verify SHA256. The only gap is that the shape of the returned job/result payload is left entirely to siblings.

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?

Schema description coverage is 100%, so the baseline is 3; the description earns a bump by explaining the idempotency_key's recovery semantics in prose (same key + same inputs to recover rather than starting a new job), which is behavioral meaning the schema pattern alone doesn't convey. It adds nothing about `pages` or `units`, which the schema already documents well.

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 precise verb+resource+scope: 'Select one-based page numbers from an uploaded PDF and return a new document containing those pages.' It explicitly distinguishes itself from pdf_merge (concatenate whole PDFs) and pdf_to_text (read text), so an agent can route correctly without opening any 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 both alternatives and the condition that selects each ('use pdf_merge to concatenate two to five whole PDFs or pdf_to_text for reading text'), which is exactly the when-to-use vs when-to-use-something-else guidance needed. It also flags prerequisites (Bearer API key, enabled backend operation, accepted payment mode) before invocation.

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.

Pdf split

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources