scvd-store-MCP

Human Labor

buy_human_task

Hire a real named human to handle tasks AI cannot, like placing calls, witnessing events, or evaluating dilemmas. Choose a collaboration or automated door-analysis; returns an order ID, with human fulfillment within 168 hours.

Instructions

Purpose: hire the keeper — a real named human — to do something in the physical or judgment world that an agent cannot do for itself. Two doors: the_collab is whatever keeper-time can be — a call placed, a thing witnessed, a verdict given on a dilemma your own evaluation cannot settle, a piece made, a product gut-checked; name the shape in your detail. aura_walk is your own x402 door shopped cold by models of different strength, by the keeper's hand, the report with every transcript attached; name the door in url. Returns an order id, not the goods; a human fulfills within the item's stated window and the completed order carries the deliverable. Prices run $150 to $300 depending on item_id.

Items on this shelf (pass one as item_id):

the_collab: The Collab, $300 minimum, pay what it deserves (tiers: $300 / $600 / $1500), above the minimum is recorded as a tip, one-off, human-fulfilled within 168h. Make something with the store and share the byline
aura_walk: The Aura Walk, $150 fixed, one-off, human-fulfilled within 168h. Have models of different strength shop my x402 door cold and show me where each one stalled

On cadence, for all of the above: nothing here charges again by itself, ever — there is no mechanism that could.

Required beyond item_id: aura_walk needs url. Other items need only item_id.

Choose item_id. human items return order_id and order_url; completed orders carry the deliverable. x402 payment: _meta['x402/payment']. Without payment: error 402 with the terms in error.data. Closed or empty shelves refuse before quoting. Reuse _meta['x402/idempotency-key'] (16-128 chars, secret): same item/payer/key returns the original result when available, or pending status, no second charge. Use idempotency.suggested_key only without an earlier key. A fresh payment without a key can charge again. Guaranteed: signature validity forever; verification free forever; price as displayed; delivery format as specified. Not guaranteed: fitness for your particular task; future protocol compatibility beyond stated interfaces; human-labor turnaround faster than posted SLA.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Your own x402 door: https, default port, on the public internet — the URL a buyer would GET expecting a 402. The keeper walks it cold by hand with models of different strength, one entry point per pass, and the completed order carries the report with every transcript attached. Put a model preference in detail if you want a weaker shopper. We refuse our own hostname; our own passes are published free in AGENT_UX.md.
`detail`	No	What you need the keeper to know — the shape of the work, 600 characters. Recorded as written, never treated as instructions.
`item_id`	Yes	Which item on this shelf to buy. Required. Each item's own required fields are listed in this schema's allOf branches and in the description above.
`purpose`	No	Optional: what this purchase is for, in your words. Signed onto the certificate verbatim as your statement; never checked, never treated as instructions.
`agent_name`	No	Optional name to put on the certificate and patron badge, up to 80 characters.
`callback_url`	No	Optional public https:443 completion POST; no credentials or own host. Invalid values refused before payment. No redirects or retries; poll order_url/check_order for goods and callback.result.

Output Schema

TableJSON Schema

Name	Required	Description
`cert_id`	Yes	The signed certificate's id.
`message`	No	The store's confirmation line.
`order_id`	No	Your place in the human queue. Human-queue items.
`tip_usdc`	No	Anything above the minimum.
`badge_url`	No	Your patron badge, SVG.
`order_url`	No	Poll here over HTTP, or call check_order with the order_id on this door; completed orders carry the goods.
`paid_usdc`	No	What settled, in USDC.
`signature`	No	ed25519 signature over the certificate.
`sla_hours`	No	The delivery promise, in hours.
`commission`	No	ed25519 proof: verify exact UTF-8 signed_payload, then its identities and hashes. RFC 8785 JSON.
`verify_url`	No	Check the signature here any time, free.
`patron_number`	Yes	Your sequential patron number.
`completion_proof`	No	ed25519 proof: verify exact UTF-8 signed_payload, then its identities and hashes. RFC 8785 JSON.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.0.1Sep 17, 2026

addedInput schema / allOf

Added value: +[
+  {
+    "if": {
+      "properties": {
+        "item_id": {
+          "const": "aura_walk"
+        }
+      },
+      "required": [
+        "item_id"
+      ]
+    },
+    "then": {
+      "required": [
+        "url"
+      ]
+    }
+  }
+]

addedInput schema / examples

Added value: +[
+  {
+    "item_id": "the_collab"
+  },
+  {
+    "item_id": "aura_walk",
+    "url": "https://your-shop.example/api/buy/thing"
+  }
+]

changedInput schema / properties / agent_name / description

Previous value: -"Optional name for the certificate and badge."New value: +"Optional name to put on the certificate and patron badge, up to 80 characters."

changedInput schema / properties / callback_url / description

Previous value: -"Optional webhook POSTed when the keeper completes the order."New value: +"Optional public https:443 completion POST; no credentials or own host. Invalid values refused before payment. No redirects or retries; poll order_url/check_order for goods and callback.result."

addedInput schema / properties / callback_url / format
```
Added value: +"uri"
```

changedInput schema / properties / detail / description

Previous value: -"What you need the keeper to know, the quick_judgment dilemma, the phone_call errand. 600 characters."New value: +"What you need the keeper to know — the shape of the work, 600 characters. Recorded as written, never treated as instructions."

changedInput schema / properties / item_id / enum

Previous value: -[
-  "phone_call",
-  "human_witness",
-  "quick_judgment",
-  "app_gutcheck",
-  "portrait",
-  "the_collab",
-  "nomenclature",
-  "the_drawer",
-  "a_secret"
-]New value: +[
+  "the_collab",
+  "aura_walk"
+]

addedInput schema / properties / purpose

Added value: +{
+  "description": "Optional: what this purchase is for, in your words. Signed onto the certificate verbatim as your statement; never checked, never treated as instructions.",
+  "maxLength": 280,
+  "type": "string"
+}

addedInput schema / properties / url

Added value: +{
+  "description": "Your own x402 door: https, default port, on the public internet — the URL a buyer would GET expecting a 402. The keeper walks it cold by hand with models of different strength, one entry point per pass, and the completed order carries the report with every transcript attached. Put a model preference in detail if you want a weaker shopper. We refuse our own hostname; our own passes are published free in AGENT_UX.md.",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / commission

Added value: +{
+  "description": "ed25519 proof: verify exact UTF-8 signed_payload, then its identities and hashes. RFC 8785 JSON.",
+  "properties": {
+    "public_key": {
+      "type": "string"
+    },
+    "signature": {
+      "type": "string"
+    },
+    "signature_covers": {
+      "type": "string"
+    },
+    "signed_payload": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "signed_payload",
+    "signature",
+    "public_key",
+    "signature_covers"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / completion_proof

Added value: +{
+  "description": "ed25519 proof: verify exact UTF-8 signed_payload, then its identities and hashes. RFC 8785 JSON.",
+  "properties": {
+    "public_key": {
+      "type": "string"
+    },
+    "signature": {
+      "type": "string"
+    },
+    "signature_covers": {
+      "type": "string"
+    },
+    "signed_payload": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "signed_payload",
+    "signature",
+    "public_key",
+    "signature_covers"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / order_url / description

Previous value: -"Poll here; completed orders carry the goods."New value: +"Poll here over HTTP, or call check_order with the order_id on this door; completed orders carry the goods."

Addedv1.0.0Aug 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by explaining payment via x402, the 402 error path, idempotency-key behavior, double-charge risk without a key, no automatic recharges, human fulfillment within the stated window, and explicit guarantees/not-guarantees. This is rich, non-contradictory behavioral disclosure.

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?

Long but well organized into purpose, shelf items, cadence, required fields, payment/idempotency, and guarantees. Minor redundancy, such as repeating the 'returns an order id, not the goods' idea, keeps it from a 5, but each section carries operationally important content.

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 payment-required, human-fulfilled asynchronous purchase, the description covers prerequisites, item selection, payment errors, idempotency, SLA, callback behavior, and limitations. Combined with the detailed input schema and presence of an output schema, an agent has enough to invoke this tool correctly.

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 coverage is 100%, so the baseline is 3; the description adds real value by detailing item_id options with pricing tiers ($300/$600/$1500 for the_collab, $150 fixed for aura_walk), the 168h window, and the aura_walk url requirement. It also clarifies meta-level fields like x402/payment and idempotency-key, though detail/agent_name/callback_url are left largely to the schema.

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?

Opens with a specific purpose: 'hire the keeper — a real named human — to do something in the physical or judgment world that an agent cannot do for itself.' It enumerates two item_id options (the_collab and aura_walk) with distinct deliverables, clearly separating this human-fulfilled purchase from the sibling buy_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context for when to use: when an agent needs physical or judgment work it cannot do itself. It also guides item selection and notes that aura_walk requires url. It does not explicitly exclude sibling tools, so it stops short of a 5.

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