StockLens

Fetch Analysis Result

fetch_analysis_result

Read-onlyIdempotent

Return the progress or result of an analysis started with initiate_analysis, by its analysis_id. Each call returns the current state once and does not wait. While status is in_progress, check again only when the person asks, and no sooner than retry_after_seconds. A failed status is an answer; relay error_message. A complete result carries the composite score and rating word, the evidence word (Full, Core or Low), each domain's score, grade word and contribution (cornerstone, major, supporting or contextual), key strengths and challenges, and for a Plus Analysis a written narrative. Say how much a domain counts only with its contribution word, never as a number or share. It does not accept a ticker and does not rank companies.

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 28, 2026

addedOutput schema / properties / result / properties / filing_facts

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "fact_type": {
+        "type": "string"
+      },
+      "filing_date": {
+        "type": "string"
+      },
+      "form_type": {
+        "type": "string"
+      },
+      "quote": {
+        "type": "string"
+      },
+      "reading": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "fact_type",
+      "reading",
+      "form_type",
+      "filing_date",
+      "quote"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / result / properties / filing_facts_note
```
Added value: +{
+  "type": "string"
+}
```

Changed5 schema fields changedSep 25, 2026
- removedOutput schema / properties / result / properties / domains / items / properties / confidence
```
Removed value: -{
-  "type": [
-    "null",
-    "number"
-  ]
-}
```
- removedOutput schema / properties / result / properties / domains / items / properties / news_key_articles / items / properties / rating
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / result / properties / domains / items / properties / news_key_articles / items / properties / tone
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / result / properties / domains / items / properties / news_key_articles / items / required
```
Previous value: -[
-  "title",
-  "publisher",
-  "url",
-  "published_at",
-  "rating",
-  "conviction"
-]New value: +[
+  "title",
+  "publisher",
+  "url",
+  "published_at",
+  "tone",
+  "conviction"
+]
```
- addedOutput schema / properties / result / properties / evidence
```
Added value: +{
+  "type": "string"
+}
```
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 only cover the read-only/idempotent safety profile; the description adds genuinely new behavior: single-shot non-waiting semantics, retry_after_seconds pacing, that a failed status is a terminal answer and error_message should be relayed, and the presentation constraint that domain weight must be expressed via the contribution word rather than a number. That is substantial disclosure beyond the structured fields.

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?

Front-loaded with purpose and packed with operational rules, and most clauses earn their place. The long enumeration of result fields (composite score, rating word, evidence word, domain grade, contributions) partly duplicates the output schema, which is the only mild redundancy.

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 an output schema covering return shape, read-only annotations covering safety, and a single required parameter, the description closes the remaining gaps: polling cadence, non-blocking semantics, error relay, and how to communicate domain weighting. Nothing needed to call or interpret it correctly is missing.

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% and the single analysis_id parameter is already documented in the schema as coming from initiate_analysis. The description restates the same provenance without adding format or validation detail, so the baseline 3 applies.

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?

States a specific verb+resource ('Return the progress or result of an analysis') and names the originating sibling tool (initiate_analysis) whose output it consumes. An agent can distinguish this from initiate_analysis and the market-data siblings without opening a schema.

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?

Explicitly states when to re-poll ('only when the person asks, and no sooner than retry_after_seconds'), that calls are non-blocking, and what the tool does not accept or do ('does not accept a ticker and does not rank companies'). This is explicit when/when-not guidance tied to the alternative path.

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?