User Intuition

Delete Participant

delete_participant

DestructiveIdempotent

Soft-delete one BYOP invitation after the user explicitly requests it. Deletion also removes its personal link. If interviews exist, the request returns a conflict unless the user separately approves deleting those interviews and cascade_interviews is true.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`cascade_interviews`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Participant deletion acknowledgement.

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

Changed5 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: +{}
```

First observedSep 30, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that deletion is a soft-delete, that the personal link is removed as a side effect, that existing interviews cause a conflict response, and that cascade requires separate user approval. The destructive/idempotent/openWorld hints are already covered by annotations, and this adds meaningful operational detail on top.

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 tight sentences, front-loaded with the action and scope, then side effects, then the failure/approval condition. No sentence is redundant and nothing important is buried.

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?

An output schema exists, so return values need no explanation, and the description covers the mutation semantics, side effects, and conflict resolution path. The only mild gap is what 'soft-delete' means for recoverability or subsequent state of the participant record.

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 description coverage is only 33%, so the description must compensate, and it does for the undocumented cascade_interviews by explaining exactly when the flag is needed and why. participant_id is self-explanatory from its UUID format, and organization_id is already documented in the schema, leaving no real gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope ('soft-delete one BYOP invitation'), which is precise enough to distinguish it from delete_interview and delete_study in the sibling list. It does not, however, explicitly name a sibling alternative, so differentiation is inferred rather than stated.

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 a clear usage condition ('after the user explicitly requests it') and spells out the conflict path when interviews exist, including the condition (user approval + cascade_interviews=true) that resolves it. It stops short of naming when to use delete_interview instead, so it is clear context without explicit alternatives.

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?