Skip to main content
Glama

FinanceQuery

Stock Screener

screener
Read-onlyIdempotent

Get results from a predefined stock screener (e.g., most-actives, day-gainers, undervalued-growth-stocks).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "screener_type": "<screener_type>"
    },
    "name": "screener"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of results to return (default: 25, max: 250)
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
screener_typeYesScreener type: most-actives | day-gainers | day-losers | growth-technology-stocks | undervalued-growth-stocks | undervalued-large-caps | aggressive-small-caps | small-cap-gainers | most-shorted-stocks | high-yield-bond | top-mutual-funds | conservative-foreign-funds | portfolio-anchors | solid-large-growth-funds | solid-midcap-growth-funds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and determinism profile is covered structurally. The description adds that the screen set is fixed/predefined, which is genuinely useful context, but says nothing about result size, ordering, or freshness beyond what the schema's count/fields parameters imply.

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?

A single sentence, front-loaded with the action and resource, followed by illustrative parenthetical examples. Nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description never explains what a 'result' is — a list of tickers, rows of metrics, or GraphQL objects shaped by the fields parameter. For a tool returning screening output that is a meaningful gap, though the parameter schema fills in most of the invocation detail.

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%, including a full enumeration of valid screener_type values and the count default/max, so the schema does the heavy lifting. The description's example values merely sample that same enum and add no syntax or behavior meaning beyond it; baseline 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 pairs a specific verb ('Get results') with a specific resource ('a predefined stock screener') and gives three concrete screener examples, so the agent can tell this is a canned screen list rather than a symbol lookup. It does not explicitly contrast itself with the many get_* retrieval siblings, so it stops short of a 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 only implied: the examples suggest 'use this when you want a ready-made list of stocks matching a theme.' The word 'predefined' hints that custom filter criteria are not supported, but the description never states when to prefer a sibling tool or what the appropriate request looks like.

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.