Skip to main content
Glama

Screen companies by criteria

screen_companies
Read-only

Filters the tracked companies on revenue growth, margins, price/sales, market cap, trend or segment, and sorts the result by one of these measures. Use it when the user asks which companies meet numeric criteria, for example revenue growth above 40% with a gross margin above 60%. A company whose filtered figure does not exist (not filed, or a ratio between two currencies) is listed separately in notComparable with the reason; it is not below the threshold.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screen_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (default 25, max 100).
trendNoOnly companies in this trend: 'up' (price above its 50-day and 200-day averages, the 50-day above the 200-day), 'down' (the reverse), 'neutral' (neither; 'flat' is accepted for it).
sortByNoSort key (default marketCap).
segmentNoRestrict to one or more segments, comma-separated, e.g. 'compute,memory,equipment'. Any of: compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other.
minMarketCapNoMinimum market capitalisation, in dollars.
minGrossMarginNoMinimum gross margin of the latest quarter, as a fraction.
maxPriceToSalesNoMaximum price / sales.
minRevenueGrowthNoMinimum revenue growth of the latest quarter against the same quarter a year earlier (a fiscal year for `basis` 'fiscal year'), as a fraction (0.4 = 40%).
minOperatingMarginNoMinimum operating margin of the latest quarter, as a fraction.
minRevenueGrowthTtmNoMinimum revenue growth over the trailing twelve months (the last four quarters against the four before; a fiscal year for `basis` 'fiscal year'), as a fraction.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / segment / description
      Previous value: -"Restrict to one or more segments, comma-separated, e.g. 'compute,memory,equipment' — any of: compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other."New value: +"Restrict to one or more segments, comma-separated, e.g. 'compute,memory,equipment'. Any of: compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other."
  2. Changed2 schema fields changed
    • addedInput schema / properties / minRevenueGrowthTtm
      Added value: +{
      +  "description": "Minimum revenue growth over the trailing twelve months (the last four quarters against the four before; a fiscal year for `basis` 'fiscal year'), as a fraction.",
      +  "type": "number"
      +}
    • changedInput schema / properties / sortBy / enum
      Previous value: -[
      -  "marketCap",
      -  "revenueGrowthYoy",
      -  "grossMargin",
      -  "operatingMargin",
      -  "priceToSales",
      -  "ytd",
      -  "day"
      -]New value: +[
      +  "marketCap",
      +  "revenueGrowthYoy",
      +  "revenueGrowthTtm",
      +  "grossMargin",
      +  "operatingMargin",
      +  "priceToSales",
      +  "ytd",
      +  "day"
      +]
  3. Changed4 schema fields changed
    • changedInput schema / properties / minGrossMargin / description
      Previous value: -"Minimum gross margin, as a fraction."New value: +"Minimum gross margin of the latest quarter, as a fraction."
    • changedInput schema / properties / minOperatingMargin / description
      Previous value: -"Minimum operating margin, as a fraction."New value: +"Minimum operating margin of the latest quarter, as a fraction."
    • changedInput schema / properties / minRevenueGrowth / description
      Previous value: -"Minimum year-on-year revenue growth, as a fraction (0.4 = 40%)."New value: +"Minimum revenue growth of the latest quarter against the same quarter a year earlier (a fiscal year for `basis` 'fiscal year'), as a fraction (0.4 = 40%)."
    • changedInput schema / properties / segment / description
      Previous value: -"Restrict to one or more segments, comma-separated, e.g. 'compute,memory,equipment,interconnect,optics' (see list_companies)."New value: +"Restrict to one or more segments, comma-separated, e.g. 'compute,memory,equipment' — any of: compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other."
  4. Changed4 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / trend / description
      Previous value: -"Only companies in this trend."New value: +"Only companies in this trend: 'up' (price above its 50-day and 200-day averages, the 50-day above the 200-day), 'down' (the reverse), 'neutral' (neither; 'flat' is accepted for it)."
    • changedInput schema / properties / trend / enum
      Previous value: -[
      -  "up",
      -  "down",
      -  "flat"
      -]New value: +[
      +  "up",
      +  "down",
      +  "neutral",
      +  "flat"
      +]
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, so safety is covered; the description adds genuinely non-obvious semantics about rows whose metric is missing being segregated into `notComparable` with a reason rather than treated as failing the threshold. It does not disclose sort direction (ascending vs descending per key), which materially affects result interpretation and matters given there is no output schema.

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 sentences with zero filler: capability and scope first, invocation guidance with a concrete example second, edge-case handling third. The example and the `notComparable` rule each earn their place.

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 10-parameter screening tool with no output schema, the description covers purpose, triggering conditions and the main correctness trap (missing metrics). Remaining gaps — sort direction, and whether default sort/limit silently apply — are minor and partly handled by the schema defaults.

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%, with units, defaults, enums and the trend definition all documented in the schema, so the description need not carry parameter detail. The description's phrase 'revenue growth, margins, price/sales, market cap, trend or segment' loosely mirrors the parameter set but adds no syntax, units or constraints beyond it. Baseline 3 is appropriate.

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 (filters tracked companies) and enumerates the exact filter dimensions plus the sort capability, so an agent knows precisely what the tool produces. It does not explicitly contrast itself with list_companies (the unfiltered sibling), which is the only notable gap.

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?

Gives a concrete when-to-use rule — 'when the user asks which companies meet numeric criteria' — plus a worked example (revenue growth above 40% with gross margin above 60%) that anchors the intended invocation. No explicit when-not conditions or named alternatives, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.