Talval

Search stocks

search_stocks

Read-onlyIdempotent

Find a company in Talval's coverage by name or ticker. Typo tolerant. Use this first when you only have a company name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many matches to return. Raise it when a name is ambiguous across listings — Shell and Unilever trade in more than one place.
`query`	Yes	Company name or ticker, e.g. 'Rheinmetall' or 'RHM.DE'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`matches`	Yes	Empty when nothing in Talval's coverage matches.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

addedInput schema / properties / limit / description

Added value: +"How many matches to return. Raise it when a name is ambiguous across listings — Shell and Unilever trade in more than one place."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "matches": {
+      "description": "Empty when nothing in Talval's coverage matches.",
+      "items": {
+        "properties": {
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sector": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ticker": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "ticker"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "matches"
+  ],
+  "type": "object"
+}

First observedSep 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds a genuine behavioral trait not present in structured data — "Typo tolerant" — which changes how an agent should phrase queries and trust near-matches.

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?

Three short sentences, front-loaded with the purpose before the routing hint. Every sentence carries information; nothing is redundant.

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?

An output schema exists, so return values need not be explained. Combined with fully documented parameters and a complete safety annotation set, the description covers what an agent needs, though a note on ambiguous-match handling would round it out.

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 both parameters are already documented, including the disambiguation rationale for `limit`. The description only echoes the name-or-ticker semantics, adding nothing the schema does not already say.

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 and resource ("Find a company") and a scope ("Talval's coverage") with the search key (name or ticker). It implicitly separates itself from screen_stocks and compare_stocks by positioning as the name-lookup entry point, but it never names those siblings explicitly.

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

Usage Guidelines4/5

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

"Use this first when you only have a company name" gives a clear condition for selecting this tool over sibling lookups. It stops short of naming alternatives (e.g., screen_stocks for filtered discovery) or stating when not to use it.

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?