TGMCharts

Screen stocks

screen_stocks

Read-onlyIdempotent

Use to find companies that meet conditions (cheap, high dividend, fast growth…). Filter and rank the covered universe (about 4,000 US-listed names) on fundamental fields (marketCap, peRatio, dividendYield, consecutiveYears, margins, 5y CAGRs, …). Returns at most 25 rows — the MCP tier's cap; the full screener lives at https://tgmcharts.com/screener. Units: yields, margins, growth and CAGRs are fractions, not percents (dividendYield gt 0.03 = above 3%; see the field description). Example: filters [{field: "dividendYield", operator: "gt", value: 0.03}, {field: "consecutiveYears", operator: "gte", value: 25}], sortBy "dividendYield".

Input Schema

Name	Required	Description
`limit`	No	Rows to return (default 10, max 25)
`format`	No	json (default): the full JSON as text. markdown: a compact table or list, fewer tokens. structuredContent is the full JSON either way.
`sortBy`	No	Sort field (default marketCap)
`filters`	No
`sortOrder`	No	Default desc
`includeEtfs`	No	Include ETFs (default false)

Output Schema

Name	Required	Description	Default
`shown`	Yes
`stocks`	Yes
`screenerUrl`	Yes
`totalMatches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / filters / items / properties / field / description

Previous value: -"Field to filter on"New value: +"Field to filter on. Units: dividendYield, netProfitMargin, grossMargin, revenueGrowth (TTM), priceChange1Y and the *Cagr5y fields are fractions (0.03 = 3%); percentFrom52WeekHigh and percentFrom52WeekLow are percents (-12.5 = 12.5% below the high); marketCap is in the quote currency (US dollars for US listings); peRatio and debtToEquity are ratios; consecutiveYears is years of dividend increases; symbol, name and sector are text (eq / neq)."

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / format

Added value: +{
+  "description": "json (default): the full JSON as text. markdown: a compact table or list, fewer tokens. structuredContent is the full JSON either way.",
+  "enum": [
+    "json",
+    "markdown"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "screenerUrl": {
+      "type": "string"
+    },
+    "shown": {
+      "type": "number"
+    },
+    "stocks": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "symbol"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalMatches": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "stocks",
+    "totalMatches",
+    "shown",
+    "screenerUrl"
+  ],
+  "type": "object"
+}

First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the hard row cap ('at most 25 rows — the MCP tier's cap') and points to the full screener at an external URL when that cap is insufficient. It also warns that units are fractions, not percents, which prevents a common silent misuse — substantial context the annotations do not carry.

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 scope, then limits, then units, then a worked example — a logical order. It is dense and the unit convention is stated twice (prose and example), but every part is useful and nothing is padded.

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?

With an output schema present, return values need not be explained, and the description covers the remaining gaps an agent needs: result cap, unit conventions, filter shape, and sort behavior. Nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (83%) and the field enum already documents units, so the baseline is 3. The description adds value by reinforcing the fraction convention ('dividendYield gt 0.03 = above 3%') and giving a concrete two-filter example plus sortBy usage that the agent can copy directly.

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 and resource — 'find companies that meet conditions' — and scopes it to 'the covered universe (about 4,000 US-listed names)' ranked on named fundamental fields. This clearly distinguishes it from siblings like compare_stocks and get_stock_summary without needing to open any schema.

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?

The opening 'Use to find companies that meet conditions (cheap, high dividend, fast growth…)' gives a clear use context, and 'Filter and rank' tells the agent what the operation does. It does not name alternatives or state exclusions (e.g. when to prefer compare_stocks or get_stock_summary), so it stops short of the top band.

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

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