User Intuition

Get Participant

get_participant

Read-onlyIdempotent

Read one BYOP invitation, including its current status, personal interview link, interview count, and reward state. Use it to verify the participant before changing their email, deleting the invitation, or sending a reward. Panel respondents are not returned by this tool.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`participant_id`	Yes
`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	The requested BYOP participant.

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"
+}

Changed20 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 / participant_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 / email / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / email / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / external_id / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / external_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / result / properties / interview_count / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / properties / interview_count / minimum
```
Added value: +-9007199254740991
```
- removedOutput schema / properties / result / properties / interview_link / $ref
```
Removed value: -"#/properties/result/properties/study_id"
```
- addedOutput schema / properties / result / properties / interview_link / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / invite_created_at / $ref
```
Removed value: -"#/properties/result/properties/reward_sent_at"
```
- addedOutput schema / properties / result / properties / invite_created_at / description
```
Added value: +"ISO 8601 timestamp."
```
- addedOutput schema / properties / result / properties / invite_created_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / invite_sent_at / $ref
```
Removed value: -"#/properties/result/properties/reward_sent_at"
```
- addedOutput schema / properties / result / properties / invite_sent_at / description
```
Added value: +"ISO 8601 timestamp."
```
- addedOutput schema / properties / result / properties / invite_sent_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / result / properties / metadata / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a safe, idempotent read, so the bar is lower. The description adds useful behavioral scope by saying panel respondents are not returned and by positioning the read as a verification step before mutations.

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?

Three sentences, each earning its place: purpose and returned fields first, usage guidance second, and the panel exclusion third. No wasted wording.

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?

With an output schema present, the description need not document return values in detail. Annotations cover safety characteristics, and the description adds enough purpose, usage, and scope context for a simple read-one tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: organization_id is documented in the schema, but participant_id has no description. The tool description does not explain either parameter or add semantic detail beyond 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 (Read) and resource (one BYOP invitation), lists the returned fields, and distinguishes the tool from list-style siblings by saying it reads one. The explicit note that panel respondents are not returned further sharpens scope.

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?

Gives clear when-to-use guidance: verify the participant before changing their email, deleting the invitation, or sending a reward. It also states an exclusion for panel respondents, though it does not explicitly name an alternative tool for that case.

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?