Skip to main content
Glama

DECA Labs

Pay for a test

start_test
Idempotent

Pay for one option of a quote and open the test. The price is the option's ad budget in USDC on Base, paid over x402. Call it first without payment: the answer is an x402 payment request for the exact amount. Pay it with an x402 client and call again with the payment as payment (the base64 PAYMENT-SIGNATURE value). A person reviews every test before its ads run; a declined test is refunded in full. Use sandbox: true to try the whole flow on Base Sepolia with test USDC; a sandbox test runs no ads and moves through its states in minutes.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "start_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionNoWhich of the quote's options to pay for. Default signal.
paymentNoThe x402 payment, base64, as an x402 client creates it. Leave out to get the payment request.
sandboxNoBase Sepolia and test USDC; no ads run. Default false.
quote_idYesThe quote_id from quote_test. Quotes hold for 30 minutes.
webhook_urlNoA public https address told of every change, signed with the webhook_secret returned once.
idempotency_keyNoAny string. Sending the same one again returns the same test and never charges twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the payment protocol (x402 on Base), pricing source (option ad budget in USDC), refund behavior for declined tests, human review of every test, and sandbox behavior on Base Sepolia with test USDC and no ads.

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

Conciseness5/5

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

The description is front-loaded with the action and payment flow, then adds sandbox behavior. Every sentence contributes operational detail without repetition or wasted framing.

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, stateful, open-world tool with no output schema, the description covers the essential flow, payment handshake, review/refund behavior, and sandbox alternative. Remaining parameter details are fully documented in the schema.

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 already 100%, so the baseline is 3. The description adds meaningful semantics for `payment` as the base64 PAYMENT-SIGNATURE value, explains omitting it to get the payment request, and clarifies that `sandbox: true` runs on Base Sepolia with test USDC and no ads.

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 uses a specific verb and resource: 'Pay for one option of a quote and open the test.' It clearly distinguishes the paid activation step from quote creation and test retrieval, so an agent can identify the action without opening other schemas.

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 an explicit two-step invocation sequence: call first without `payment` to receive an x402 payment request, then call again with the base64 payment signature. It also says when to use `sandbox: true` and explains the human-review/refund condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources