Popdot AI

answer_trial_canary

Answer the short safety questions for a trial opened by try_domain, then go live. Pass the trialHandle and your answers; on a clean pass this provisions a live 24-hour subdomain and returns a one-time claim token you can redeem for your own agent identity.

Input Schema

TableJSON Schema

Name	Required	Description
`answers`	Yes	Your answers to the safety questions, one { question_id, response } per question.
`publicKey`	No	Optional, on the call that goes live. Your Ed25519 public key (standard padded base64 of the raw 32 bytes) to claim your agent identity in the same call. Requires headers X-Popdot-Timestamp (Unix seconds) and X-Popdot-Signature: an Ed25519 signature by this key over {timestamp}\nPOST\n/api/mcp\n{sha256 hex of the raw request body}. Omit it to receive a claim token for upgrade_trial instead.
`trialHandle`	Yes	The trialHandle returned by try_domain.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No
`sigil`	No
`reason`	No
`status`	No
`sigilId`	No
`trialId`	No
`upgrade`	No
`expiresAt`	No
`retryable`	No
`claimError`	No
`claimToken`	No
`candidateId`	No
`shareMessage`	No
`trustReceipt`	No
`canaryVerdict`	No
`scorerVersion`	No
`claimTokenExpiresAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026

addedInput schema / properties / publicKey

Added value: +{
+  "description": "Optional, on the call that goes live. Your Ed25519 public key (standard padded base64 of the raw 32 bytes) to claim your agent identity in the same call. Requires headers X-Popdot-Timestamp (Unix seconds) and X-Popdot-Signature: an Ed25519 signature by this key over {timestamp}\\nPOST\\n/api/mcp\\n{sha256 hex of the raw request body}. Omit it to receive a claim token for upgrade_trial instead.",
+  "type": "string"
+}

addedOutput schema / properties / claimError

Added value: +{
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / sigil

Added value: +{
+  "properties": {
+    "agentName": {
+      "type": "string"
+    },
+    "mandateId": {
+      "type": "string"
+    },
+    "publicKey": {
+      "type": "string"
+    },
+    "sigilId": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sigilId",
+    "publicKey",
+    "mandateId"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / sigilId
```
Added value: +{
+  "type": "string"
+}
```

Changed4 schema fields changedAug 27, 2026

addedOutput schema / properties / canaryVerdict
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / scorerVersion
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / trustReceipt / properties

Added value: +{
+  "canaryVerified": {
+    "type": "boolean"
+  },
+  "claimable": {
+    "type": "boolean"
+  }
+}

addedOutput schema / properties / upgrade / properties

Added value: +{
+  "agentPaymentAvailable": {
+    "type": "boolean"
+  },
+  "availableDurations": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "preserveExactUrl": {
+    "type": "boolean"
+  }
+}

AddedAug 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations are minimal (readOnlyHint false, openWorldHint true). The description adds important context: it provisions a live 24-hour subdomain, returns a one-time claim token, and mentions a 'clean pass' implying possible failure. This goes beyond annotations, though it does not disclose all side effects like irreversibility.

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 two sentences with no fluff, clearly front-loading the purpose and outcome. It is efficient and easy to parse.

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?

The description covers the main flow and result, and with an output schema available, return values are documented elsewhere. It could mention failure conditions or relationship to upgrade_trial more explicitly, but it is largely complete for an agent to understand the tool's role.

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% with each parameter having a description. The tool description only mentions passing trialHandle and answers, which matches the schema. It does not add extra format or usage details beyond what the schema provides, so baseline 3 is appropriate.

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 states a clear action: answer safety questions for a trial opened by try_domain, then go live. It specifies the resource (trial) and the outcome (provision subdomain, claim token). It distinguishes from siblings like try_domain and upgrade_trial by describing the specific flow.

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?

It implies usage after try_domain, but does not explicitly state when not to use or mention alternatives like upgrade_trial. The context is clear that it's for answering safety questions, but there is no exclusion criteria.

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

All Popdot AI 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.