User Intuition

Launch Panel

launch_panel

Destructive

Launch paid recruitment for an existing Panel study using a current estimate_id from estimate_panel. Require approval of the saved plan and separate explicit approval of the complete estimate, including resolved country and language, credit cost, balance, card hold, and heuristic timeline. The backend rejects an expired estimate or changed study, launch inputs, balance, or price. A launch fields exactly one country selected by the user. Below 10% incidence or over 1,000 interviews, use submit_feasibility_request.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`target`	Yes
`study_id`	Yes
`frequency`	No		one-time
`estimate_id`	Yes	Current estimate identifier from estimate_panel. Paid launch fails if the study, inputs, balance, or price changed, or the estimate expired.
`country_code`	Yes	Required explicit country code from userintuition://catalog/panel-countries. Never infer a country.
`incident_rate`	Yes	Percentage points. Values below 10 require submit_feasibility_request instead of direct launch.
`idempotency_key`	No	Reuse the same key and inputs if a prior call timed out. A different operation needs a new key.
`organization_id`	No	Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Panel launch acknowledgement or dry-run estimate.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / organization_id

Added value: +{
+  "description": "Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed36 schema fields changedSep 30, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / study_id / pattern
```
Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
```
- changedOutput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- changedOutput schema / properties / result / additionalProperties
```
Previous value: -trueNew value: +{}
```
- removedOutput schema / properties / result / properties / available_credit_balance / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / available_credit_balance / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / card_hold_usd / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / card_hold_usd / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / country_code / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / country_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / credit_cost_per_interview / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / credit_cost_per_interview / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / credit_deficit / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / credit_deficit / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / estimate_id / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / estimate_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / estimated_timeline_hours / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / estimated_timeline_hours / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / estimated_total_cost_usd / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / estimated_total_cost_usd / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / expires_at / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / expires_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / frequency / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / frequency / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / language_code / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / language_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / panel_status / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / panel_status / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / reward_per_interview_usd / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / reward_per_interview_usd / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / sufficient_credits / $ref
```
Removed value: -"#/properties/result/properties/dry_run"
```
- addedOutput schema / properties / result / properties / sufficient_credits / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / result / properties / target / anyOf
```
Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / result / properties / total_credit_cost / $ref
```
Removed value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / total_credit_cost / type
```
Added value: +[
+  "number",
+  "null"
+]
```
First observedSep 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare destructive/non-idempotent/openWorld, and the description adds substantial context beyond them: backend rejection conditions (expired estimate, changed study, inputs, balance, price), the required dual approval, and the one-country-per-launch constraint. It also implies the launch is irreversible paid spend.

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 the action and its prerequisite, then failure modes, then the escalation rule. Dense but each sentence carries operational weight; slightly long but no filler.

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?

An output schema exists so return values need no explanation; the description covers prerequisites, rejection conditions, single-country constraint, and the sibling escalation path. Complete for a destructive, paid mutation.

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 63%, and the description reinforces the semantics of the highest-risk params (estimate_id recency/invalidation, explicit country_code, incident_rate threshold). It adds reasoning beyond the field descriptions, though frequency and organization_id are left 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?

States a specific verb (Launch) and resource (paid recruitment for an existing Panel study), and ties the required estimate_id back to the estimate_panel sibling so the agent knows the prerequisite flow. Clearly distinguishable from create_study and submit_feasibility_request.

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?

Explicitly names the escalation alternative and its trigger: 'Below 10% incidence or over 1,000 interviews, use submit_feasibility_request.' Also states prerequisite approvals for the plan and the resolved estimate before launch.

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

All User Intuition 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?