Talval

Get stock research

get_stock_research

Read-onlyIdempotent

Talval's valuation verdict, fair-value estimate, upside, quality/safety/value scores and latest filed results for one ticker. End-of-day snapshot with a date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ticker`	Yes	Exact ticker as Talval lists it, e.g. 'AAPL', 'RHM.DE', 'PRU.L'.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No
`name`	No
`as_of`	No	Date of the verdict snapshot, YYYY-MM-DD.
`price`	No
`scores`	No	0-100, null where the inputs behind a score are missing.
`sector`	No
`ticker`	Yes
`country`	No
`covered`	Yes	False when Talval does not cover this ticker; every other field is then null.
`verdict`	No	Undervalued, Fairly valued or Overvalued.
`currency`	No	Trading currency of price and fair value.
`industry`	No
`conviction`	No	1-10.
`fair_value`	No	Null when withheld — see fair_value_usable and withheld_reason.
`market_cap`	No
`risk_level`	No
`upside_pct`	No	Percent, not a fraction.
`pe_trailing`	No
`price_as_of`	No
`latest_annual`	No	As reported in the company's own filings — not estimates.
`withheld_reason`	No	Why fair_value is null, when it is.
`fair_value_usable`	No	False when the company reports in a different currency than it trades in, which makes every price-to-fundamentals figure cross-currency nonsense. A false here is a deliberate suppression, not missing data.
`dividend_yield_pct`	No	Forward yield as a PERCENT, e.g. 2.9 for 2.9%.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "as_of": {
+      "description": "Date of the verdict snapshot, YYYY-MM-DD.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "conviction": {
+      "description": "1-10.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "country": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "covered": {
+      "description": "False when Talval does not cover this ticker; every other field is then null.",
+      "type": "boolean"
+    },
+    "currency": {
+      "description": "Trading currency of price and fair value.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dividend_yield_pct": {
+      "description": "Forward yield as a PERCENT, e.g. 2.9 for 2.9%.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "fair_value": {
+      "description": "Null when withheld — see fair_value_usable and withheld_reason.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "fair_value_usable": {
+      "description": "False when the company reports in a different currency than it trades in, which makes every price-to-fundamentals figure cross-currency nonsense. A false here is a deliberate suppression, not missing data.",
+      "type": "boolean"
+    },
+    "industry": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "latest_annual": {
+      "description": "As reported in the company's own filings — not estimates.",
+      "properties": {
+        "eps_diluted": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "fiscal_year": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "free_cash_flow": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "net_income": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "revenue": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "market_cap": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pe_trailing": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "price": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "price_as_of": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "risk_level": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "scores": {
+      "description": "0-100, null where the inputs behind a score are missing.",
+      "properties": {
+        "composite": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "dividend": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "piotroski_f_score": {
+          "description": "0-9.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "quality": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "safety": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "sector": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ticker": {
+      "type": "string"
+    },
+    "upside_pct": {
+      "description": "Percent, not a fraction.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verdict": {
+      "description": "Undervalued, Fairly valued or Overvalued.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "withheld_reason": {
+      "description": "Why fair_value is null, when it is.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "ticker",
+    "covered"
+  ],
+  "type": "object"
+}

First observedSep 21, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds a valuable behavioral trait not in annotations: the data is an 'End-of-day snapshot with a date,' signalling non-real-time freshness and a dated result. This is a clear addition beyond structured fields, though not a rich behavioral profile.

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?

Two tightly written sentences: the first front-loads the returned fields, the second adds the snapshot timing. Every clause carries information and there is no repetition or filler.

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 one-ticker retrieval tool with a rich output schema and safety annotations, the description covers what is returned and the snapshot nature. It lacks explicit sibling routing, which would help an agent distinguish it from search_stocks and screen_stocks, but the core call context is otherwise complete.

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 description coverage is 100%, and the ticker parameter's schema already documents the exact format with examples ('AAPL', 'RHM.DE', 'PRU.L'). The description only reinforces 'for one ticker,' adding no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 names the specific data returned (valuation verdict, fair-value estimate, upside, quality/safety/value scores, latest filed results) for a single ticker, making the tool's purpose clear. It implicitly distinguishes from siblings like screen_stocks and compare_stocks by stating 'for one ticker,' but never explicitly names alternatives.

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 explicit guidance on when to use this tool versus siblings such as search_stocks or screen_stocks, nor any prerequisites or exclusions. The single-ticker scope implies a narrow usage, but the description leaves the agent to infer this without confirmation.

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

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