get_feasibility_requestGet one feasibility request and its status or estimate.
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes | ||
| organization_id | No | Organization for this operation and billing. Use list_organizations to choose an active membership. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | The requested feasibility request. |
Changes observed during successful MCP inspections.
Input schema / properties / organization_id / descriptionPrevious 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."Input schema / properties / organization_idAdded 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"
+}Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / request_id / patternAdded 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)$"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / properties / result / additionalPropertiesPrevious value: -trueNew value: +{}Output schema / properties / result / properties / cancelled_at / $refRemoved value: -"#/properties/result/properties/responded_at"Output schema / properties / result / properties / cancelled_at / descriptionAdded value: +"ISO 8601 timestamp."Output schema / properties / result / properties / cancelled_at / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / result / properties / estimated_timeline_hours / $refRemoved value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"Output schema / properties / result / properties / estimated_timeline_hours / typeAdded value: +[
+ "number",
+ "null"
+]Output schema / properties / result / properties / estimated_total_cost_usd / $refRemoved value: -"#/properties/result/properties/estimated_total_cost_per_interview_usd"Output schema / properties / result / properties / estimated_total_cost_usd / typeAdded value: +[
+ "number",
+ "null"
+]Output schema / properties / result / properties / expected_response_by / $refRemoved value: -"#/properties/result/properties/responded_at"Output schema / properties / result / properties / expected_response_by / descriptionAdded value: +"ISO 8601 timestamp."Output schema / properties / result / properties / expected_response_by / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / result / properties / target / maximumAdded value: +9007199254740991Output schema / properties / result / properties / target / minimumAdded value: +-9007199254740991Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds that the response may contain a status or an estimate depending on request state, which is genuinely useful beyond annotations, but permission requirements or behavior for unknown IDs is not mentioned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with zero filler, front-loading the verb and resource. The trailing 'status or estimate' slightly muddies whether both are returned or one is conditional.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 the tool is a simple two-param read. Still, the description gives no guidance on how a not-found or pending request behaves, nor routes to the companion list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%: organization_id carries a description pointing to list_organizations, and request_id is well-typed as a UUID with format and pattern constraints. The description adds nothing about either parameter, so it neither helps nor hurts, making a baseline 3 appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get one feasibility request') and clarifies the returned payload includes status or estimate. The word 'one' distinguishes it from the sibling list_feasibility_requests, though the sibling is not named.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The singular 'one' implies the tool is used when a specific request_id is already known, and the sibling list_feasibility_requests covers discovery. However, the description never states when to use this versus the list tool or cancel_feasibility_request, leaving the agent to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.