Skip to main content
Glama
tearsheet

tearsheet

by kewonit

search_screen_fields

Read-only

Find exact screener field names, units, and periods for stock screening by keyword, including preset screens when querying "presets".

Instructions

Find exact screener field names, with their units and periods.

    screen_stocks needs exact field names, such as "ROCE" or "3yr Avg ROCE".
    Search by words, like "roce" or "debt equity". Also lists the preset
    screens when query is "presets". Searching is local and cheap.
    

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": {
      "query": "<query>"
    },
    "name": "search_screen_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, but the description still adds real context: searching is local and cheap, so no cost or rate-limit caution is needed before calling, and results include units and periods. The 'presets' branch is an extra behavioral mode not inferable from the schema.

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?

Four short sentences, front-loaded with the core purpose and followed by the motivating consumer and the special case. Minor redundancy in the example phrase 'such as "ROCE" or "3yr Avg ROCE"', but nothing wasted overall.

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?

Low complexity, output schema present, and the description covers purpose, motivating workflow, search style, and the presets mode. The only meaningful gap is the unmentioned limit/cap behavior on result count, which is minor for a local search tool.

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 0%, so the description must carry parameter meaning. It does well on 'query' (word-based search plus the exact string 'presets' triggering a preset-screen listing), but the 'limit' parameter (default 15, max 50) is never mentioned, leaving one of two params undocumented everywhere.

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 exact screener field names') plus what comes back ('with their units and periods'). It also names the consuming sibling, screen_stocks, so an agent can distinguish discovery from execution without opening either 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?

Gives clear precondition-style guidance: screen_stocks needs exact field names, so search here first when you only have loose words like 'roce' or 'debt equity'. It also documents the special mode query='presets'. No explicit when-not-to-use case is stated, which keeps it below a 5.

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