User Intuition

Estimate Panel

estimate_panel

Read-onlyIdempotent

Read-only estimate for one Panel recruitment cycle. Returns per-interview and total credit cost, available balance and deficit, participant reward, card hold, recurrence, and a heuristic timeline. Ask for explicit approval of the estimate before any paid launch. The price and balance can change before launch; use submit_feasibility_request for incidence below 10% or more than 1,000 interviews.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`target`	Yes
`study_id`	Yes
`frequency`	No		one-time
`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.
`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	Read-only panel estimate for one recruitment cycle.

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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely non-structured context: that the price and balance can change before launch, and that an explicit approval step precedes any paid launch. It also lists the returned fields, which is partly redundant given the output schema exists.

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?

Three tight sentences, front-loaded with the core purpose, followed by the approval gate and the routing rule. The enumeration of return fields (cost, balance, deficit, reward, card hold, recurrence, timeline) is the only slightly padded element since an output schema exists.

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 read-only estimation tool with 6 params, an output schema and rich annotations, the description covers purpose, the approval workflow, staleness caveat, and the sibling-routing rule. An agent has everything needed to call it and interpret the result 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 only 50%, but the description supplies the key semantic threshold for incident_rate (<10 routes elsewhere) and the practical ceiling tying to target's 1000 maximum. Country-code provenance is already documented in the schema, so the description sensibly doesn't repeat it.

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 and resource plus scope: 'Read-only estimate for one Panel recruitment cycle.' This clearly separates it from launch_panel (which spends money) and submit_feasibility_request (which handles edge cases), so an agent can route without opening the schema.

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?

Names the explicit workflow gate ('Ask for explicit approval of the estimate before any paid launch') and the alternative with its triggering condition ('use submit_feasibility_request for incidence below 10% or more than 1,000 interviews'). Both when-to-use and when-to-use-something-else are present.

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?