Paddock Cards

Open private uploads

open_private_content

Open a private upload scope for the buyer’s photo, artwork, logo or QR card. Omit both inputs for a new scope, or pass an unpaid order and its token to reopen that draft’s scope. Returns scope_id, a private token, upload_url and expiry. Assistants cannot upload conversation attachments; send the buyer the link, then use read_private_content when they finish. Catalog cards need no upload scope.

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": "open_private_content"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	No	Existing unpaid order.id from prepare_order, revise_order or read_order. Supply its matching order_access_token to reopen that draft’s upload scope; omit both fields for a new scope.
`order_access_token`	No	Matching private token for the existing unpaid order, returned by prepare_order, revise_order or its open_private_content scope. Required with order_id; omit both for a new scope. Never invent a token.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / order_access_token / description

Previous value: -"The private capability returned by open_private_content. Never invent one."New value: +"Matching private token for the existing unpaid order, returned by prepare_order, revise_order or its open_private_content scope. Required with order_id; omit both for a new scope. Never invent a token."

changedInput schema / properties / order_id / description

Previous value: -"With order_access_token: reopen the private scope of an existing unpaid draft so the buyer can add a picture to it, then replace its cards with revise_order. Omit both to start a new scope."New value: +"Existing unpaid order.id from prepare_order, revise_order or read_order. Supply its matching order_access_token to reopen that draft’s upload scope; omit both fields for a new scope."

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare this is a non-readonly, non-idempotent, non-destructive write, and the description adds real behavioral context: returns a private token and expiring upload_url, assistants cannot push conversation attachments, and the human must be sent the link. It does not state scope lifetime, renewal behavior, or what happens when a scope expires, which keeps it from 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.

Conciseness4/5

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

Front-loaded with purpose, then branching rules, then return values, then caveats — a sensible order with no filler sentences. The 'Returns scope_id, a private token, upload_url and expiry' sentence partly duplicates the existing output schema, a minor redundancy.

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?

Given an output schema exists, the description need not detail return structure, yet it still flags the key return values and the expiry. Combined with the workflow handoff to read_private_content and the human-in-the-loop constraint, an agent has everything needed to call this correctly.

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 both parameters already document the pairing rule ('Required with order_id; omit both for a new scope'), so the description largely restates the schema. It adds the useful constraint that a token must never be invented, but nothing about format or validation beyond the pattern already present.

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 ('Open a private upload scope') and immediately delimits what the scope is for (buyer's photo, artwork, logo, QR card). It is clearly distinguishable from read_private_content, compose_private_card and prepare_order, which are named or implied.

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?

Both branches are spelled out explicitly: omit both inputs for a new scope, or pass an unpaid order plus token to reopen a draft's scope. It names the follow-up alternative (read_private_content) and states a real exclusion ('Catalog cards need no upload scope'), so an agent knows when not to call it.

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

All Paddock Cards 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.

Resources

Need Help?