Talval

Screen stocks

screen_stocks

Read-onlyIdempotent

Run one of Talval's stock screens over the covered universe and return the ranked results with fair value, upside and scores.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	How many ranked rows to return. The screen is already ranked, so a smaller number gives the strongest names rather than a sample.
`screen`	Yes	Which screen to run.
`sector`	No	Optional sector filter, e.g. 'Technology'.

Output Schema

TableJSON Schema

Name	Required	Description
`rows`	Yes	Ranked. Empty when nothing clears the screen.
`label`	No
`screen`	Yes
`sector`	No	The sector filter applied, if any.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

addedInput schema / properties / limit / description

Added value: +"How many ranked rows to return. The screen is already ranked, so a smaller number gives the strongest names rather than a sample."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "label": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "rows": {
+      "description": "Ranked. Empty when nothing clears the screen.",
+      "items": {
+        "properties": {
+          "currency": {
+            "description": "Trading currency of the price and fair value.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "fair_value": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "price": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "quality_score": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "ticker": {
+            "type": "string"
+          },
+          "upside_pct": {
+            "description": "Percent, not a fraction: 12.5 means +12.5%.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "verdict": {
+            "description": "Undervalued, Fairly valued or Overvalued.",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "ticker"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "screen": {
+      "type": "string"
+    },
+    "sector": {
+      "description": "The sector filter applied, if any.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "screen",
+    "rows"
+  ],
+  "type": "object"
+}

First observedSep 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds that output is ranked and includes fair value, upside and scores, but with an output schema present even that is partly redundant. Modest added value.

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?

One tight sentence that front-loads the verb, the source of the screens, and the shape of the result. Nothing extraneous.

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?

With full schema coverage, rich annotations and an output schema, the description only needs to orient the agent, which it does. It is slightly thin on how this differs from the other stock-listing siblings, but nothing required for a correct call 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 description coverage is 100%, so all three parameters are already documented, including the important note that limit selects the strongest names rather than a sample. The description adds no syntax or semantics 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?

States a specific verb (run) and resource (Talval's stock screens) and describes the returned payload (ranked results with fair value, upside and scores). It does not name a sibling to differentiate from search_stocks or get_stock_research, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is implied by the screen enum and the 'covered universe' framing, but there is no explicit when-to-use-this-vs-alternatives guidance, e.g. versus search_stocks for arbitrary lookups. A reader can infer intent but is not told the boundary.

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?