Arckép

create_book_upload

Initialize a direct multipart S3 upload for a book scan up to 500 MiB (PDF or ZIP of page scans).

Returns key, upload_id, part_size (16 MiB) and presigned PUT part_urls. Upload each slice via HTTP PUT, collect its ETag response header in order, and finish with complete_book_upload before calling create_book. For scans up to 100 MiB that already have a public HTTPS URL, pass file_url directly to create_book instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "create_book_upload"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description adds the real behavior that matters: this only initializes an upload session, part_size is 16 MiB, each slice must be PUT over HTTP and its ETag captured in order, and the session is incomplete until complete_book_upload runs. That ordering constraint is exactly the kind of operational detail annotations cannot convey.

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?

Three tightly packed sentences with the core action front-loaded and the alternative path last, which is the right order. The enumerated return fields overlap with the existing output schema, so that clause is slightly redundant, but nothing else is wasted.

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 multi-step upload flow with one compound parameter and an output schema, the description supplies everything an agent needs: limits, format rules, the full call sequence, the ETag requirement, and the cheap alternative for small files. No essential behavioral question is left open.

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?

Top-level coverage is 0% (the 'request' wrapper is undocumented), but the description compensates with the 500 MiB bound and the PDF/ZIP constraint that map onto size_bytes and mime. The nested schema already documents name, mime and size_bytes individually, so the description adds routing meaning rather than new per-field semantics -- useful but not exhaustive.

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 -- 'Initialize a direct multipart S3 upload for a book scan' -- plus the accepted formats and size ceiling. An agent can immediately separate it from create_book (final creation) and complete_book_upload (finish step) 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?

Gives an explicit ordered workflow (upload slices, collect ETags, call complete_book_upload, then create_book) and an explicit exclusion with an alternative path: scans under 100 MiB with a public HTTPS URL should pass file_url to create_book instead. Both 'when' and 'when not' are stated.

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

All Arckép 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.