StockLens

Fetch Analysis Result

fetch_analysis_result

Read-onlyIdempotent

Fetch the result or progress of a previously initiated StockLens analysis. Returns status (in_progress/complete/failed), progress percentage, and full result when complete. Each call returns the current state once; it does not wait for completion. While status is in_progress, retry_after_seconds is the earliest sensible time to check again — check again only if the user asks to continue. Complete results include composite score, domain breakdowns, key insights, and may include a Plus Analysis AI narrative. Does NOT start a new analysis and does NOT rank or screen stocks — call discover_stocks for a multi-stock list. Does NOT accept a ticker; only the analysis_id from initiate_analysis.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`analysis_id`	Yes	The analysis_id returned by initiate_analysis

Output Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	Yes
`result`	No
`status`	Yes
`analysis_id`	Yes
`progress_pct`	No
`error_message`	No
`retry_after_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedOutput schema / properties / result / properties / domains / items / properties / contribution
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / result / properties / domains / items / properties / weight
```
Removed value: -{
-  "type": [
-    "null",
-    "number"
-  ]
-}
```

Changed2 schema fields changedSep 5, 2026

addedOutput schema / properties / scope

Added value: +{
+  "enum": [
+    "single_analysis_result"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "analysis_id",
-  "status"
-]New value: +[
+  "analysis_id",
+  "status",
+  "scope"
+]

Changed4 schema fields changedAug 19, 2026

addedOutput schema / properties / result / properties / domains / items / properties / confidence
```
Added value: +{
+  "type": [
+    "null",
+    "number"
+  ]
+}
```

addedOutput schema / properties / result / properties / domains / items / properties / insider_key_metrics

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "label",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / result / properties / domains / items / properties / news_key_articles

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "conviction": {
+        "type": "number"
+      },
+      "published_at": {
+        "type": "string"
+      },
+      "publisher": {
+        "type": "string"
+      },
+      "rating": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "publisher",
+      "url",
+      "published_at",
+      "rating",
+      "conviction"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / result / properties / domains / items / properties / weight
```
Added value: +{
+  "type": [
+    "null",
+    "number"
+  ]
+}
```

First observedAug 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context: it does not wait for completion, returns the current state once, and explains what complete results include. This goes beyond the annotations and clarifies the non-blocking, one-shot nature of the call.

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?

The description is well-structured and front-loaded with the core purpose, then details about statuses, retry behavior, and exclusions. It is slightly longer than necessary but every sentence adds functional value, and the logical flow is clear.

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

Completeness5/5

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

Given the tool's complexity, the description covers all essential aspects: status values, progress, retry timing, complete result contents, and explicit exclusions. The presence of an output schema means return format details are not needed, and the description fully equips an agent to call it correctly.

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 the parameter analysis_id is fully described in the schema. The description reiterates that it must come from initiate_analysis and that no ticker is accepted, but this does not add substantial semantic value beyond the schema. Baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool fetches the result or progress of a previously initiated StockLens analysis, using a specific verb and resource. It explicitly distinguishes itself from siblings by stating it does NOT start a new analysis, does NOT rank or screen stocks, and does NOT accept a ticker, which makes it unambiguous among the sibling tools.

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

Usage Guidelines5/5

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

It provides explicit when-to-use guidance: after initiate_analysis, and when-not-to-use: for multi-stock lists use discover_stocks, and it clarifies that it only accepts analysis_id. It also gives retry guidance with retry_after_seconds and advises checking again only if the user asks to continue, leaving no ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All StockLens 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?