User Intuition

Create Research Session

create_research_session

Create a research session (a saved analysis workspace) for selected studies and uploaded sources. Reuse the same idempotency key after an uncertain response.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_research_session"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Display name for the research session or saved output.	Research session
`idempotency_key`	Yes	Use a stable key for this operation and reuse it on retries with the same inputs.
`organization_id`	No	Organization for this operation and billing. Use list_organizations to choose an active membership.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedInput schema / properties / idempotency_key / description

Added value: +"Use a stable key for this operation and reuse it on retries with the same inputs."

addedInput schema / properties / name / description

Added value: +"Display name for the research session or saved output."

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / organization_id / description

Previous value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."

AddedOct 19, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent mutation, and the description usefully adds the retry contract: the idempotency key must be reused after an uncertain response, which is exactly the missing behavioral detail for an idempotentHint=false tool. It doesn't cover permissions or what happens to the session afterwards, keeping it below a 5. The retry guidance complements rather than contradicts the idempotentHint=false annotation.

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?

Two tight sentences: purpose first, then the retry rule front-loaded where it matters. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema means return values need not be described, and idempotency is handled well. But the description leaves unclear how studies and sources are attached if they are not parameters, and gives no permission or post-creation context for a mutation tool.

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%, so name, idempotency_key and organization_id are already documented, and the description correctly reinforces idempotency key reuse. However, it emphasizes 'selected studies and uploaded sources' while no such parameters exist in the schema, which can mislead an agent about what must be supplied at creation time.

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 ('Create a research session') and clarifies the resource with a parenthetical gloss ('a saved analysis workspace'). This is enough to separate it from sibling create_* tools such as create_study or create_webhook, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is the retry instruction ('Reuse the same idempotency key after an uncertain response'), which is operational rather than selection advice. It never says when to create a session versus using chat_research_session or add_all_research_studies, nor are any prerequisites or exclusions given.

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.