User Intuition

List Feasibility Requests

list_feasibility_requests

Read-onlyIdempotent

List the account feasibility requests, newest first, in bounded pages.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No
`page_size`	No
`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	A bounded page of account feasibility requests.

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

Changed24 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 / page / maximum
```
Added value: +9007199254740991
```
- 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: +{}
```
- addedOutput schema / properties / result / properties / page / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / properties / page / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / result / properties / page_size / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / properties / page_size / minimum
```
Added value: +-9007199254740991
```
- changedOutput schema / properties / result / properties / requests / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
- removedOutput schema / properties / result / properties / requests / items / properties / cancelled_at / $ref
```
Removed value: -"#/properties/result/properties/requests/items/properties/responded_at"
```
- addedOutput schema / properties / result / properties / requests / items / properties / cancelled_at / description
```
Added value: +"ISO 8601 timestamp."
```
- addedOutput schema / properties / result / properties / requests / items / properties / cancelled_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / requests / items / properties / estimated_timeline_hours / $ref
```
Removed value: -"#/properties/result/properties/requests/items/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / requests / items / properties / estimated_timeline_hours / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / requests / items / properties / estimated_total_cost_usd / $ref
```
Removed value: -"#/properties/result/properties/requests/items/properties/estimated_total_cost_per_interview_usd"
```
- addedOutput schema / properties / result / properties / requests / items / properties / estimated_total_cost_usd / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / result / properties / requests / items / properties / expected_response_by / $ref
```
Removed value: -"#/properties/result/properties/requests/items/properties/responded_at"
```
- addedOutput schema / properties / result / properties / requests / items / properties / expected_response_by / description
```
Added value: +"ISO 8601 timestamp."
```
- addedOutput schema / properties / result / properties / requests / items / properties / expected_response_by / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / result / properties / requests / items / properties / target / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / properties / requests / items / properties / target / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / result / properties / total_count / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result / properties / total_count / minimum
```
Added value: +-9007199254740991
```
First observedSep 30, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description does add the useful behavioral facts of newest-first ordering and bounded (paginated) results, but says nothing about page size ceiling behavior or empty results.

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?

A single tight sentence with the resource and ordering front-loaded and no filler. It is efficient, though its brevity is partly under-specification rather than pure conciseness.

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?

With an output schema present, return values need not be explained, and annotations carry the safety profile. Still, for a paginated list with an admin-scoped filter, the description leaves the paging contract and the relationship to sibling feasibility tools implicit.

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 coverage is only 33% – only organization_id is described. The description mentions 'bounded pages' but does not explain page/page_size semantics, defaults (1 and 20), or the 100-item cap, and adds nothing about the admin-only organization_id scoping beyond what the schema says.

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 (list) and resource (feasibility requests) scoped to the account, and adds ordering (newest first). It is distinguishable from get_feasibility_request and submit/cancel by name, though it never explicitly contrasts with those siblings.

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?

There is no when-to-use guidance: nothing says when to page through this list versus fetching a single request via get_feasibility_request, or how it relates to submit/cancel. Usage is only implied by the verb 'List'.

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?