User Intuition

List Feasibility Requests

list_feasibility_requests

Read-onlyIdempotent

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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."

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

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral details: newest-first ordering and bounded pagination, but it does not describe auth requirements, error conditions, or return characteristics beyond what annotations and the output schema provide.

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?

The description is a single front-loaded sentence with no wasted wording. It efficiently conveys the core action, scope, ordering, and pagination behavior.

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?

For a simple list tool with rich annotations and an output schema, the description covers purpose, ordering, and pagination adequately. It leaves parameter usage details to the schema, which is reasonable, though it could mention how it relates to get_feasibility_request.

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 33%, so the description should compensate for undocumented parameters. It mentions 'bounded pages' but does not explain page or page_size semantics, defaults, or limits; organization_id is documented separately in the schema.

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?

The description states a specific verb and resource: list the account feasibility requests. It adds ordering and pagination details, making the scope clear, though it does not explicitly contrast with get_feasibility_request or other 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?

The description gives no explicit guidance on when to use this tool versus get_feasibility_request or other alternatives. The listing purpose is implied, but there are no exclusions or prerequisites.

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?