Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Preset screeners

screener_presets
Read-onlyIdempotent

List Stockbit's preset and guru screener groups, or browse the screeners inside a chosen group by passing its parent_id, to find ready-made filters for valuation, technical, dividend and other strategies.

Instructions

Stockbit's ready-made (guru and preset) screeners.

Returns (Stockbit's data field): Without parent_id: data[{id, name, description, image_url}] - known group ids 26 Guru, 27 Popular, 28 Valuation, 29 Technical, 30 Dividen, 31 Fundamental, 32 Bandarmology, 33 Overview. With parent_id: data[{id, name, description, type, favorite}] - open one with GET /screener/templates/{id}?type=...

Paywall: unknown (user notes: Bandarmology metrics need Stockbit Pro).

Endpoint: GET exodus /screener/preset.

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": {
      "mobile": "<mobile>"
    },
    "name": "screener_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
mobileYesAlways 'true' in the URL Default "true".
parent_idNoOmit = list preset groups; set = list screeners in that group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes well beyond that: it spells out the returned data fields for both modes, enumerates the known group ids 26-33 with their meanings, notes a paywall caveat for Bandarmology metrics, and gives the underlying endpoint. That is substantive behavioral context no annotation supplies.

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?

The purpose is front-loaded in the first line, followed by clearly separated Returns, Paywall, and Endpoint blocks that are easy to scan. The listing of all eight group ids is a dense data dump that borders on bloat, but it earns its space as the only source of those values.

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?

With no output schema, the description correctly takes on the burden of describing return fields for both modes and adds the next-step endpoint for opening a screener. The remaining gap is routing guidance relative to siblings and any pagination or size expectations for the group listing.

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 100%, so both parameters are already documented, but the description adds real value by enumerating valid parent_id values (26 Guru through 33 Overview) with labels, which the schema's bare integer constraint does not convey. It stops short of describing whether the group list is stable or complete.

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 names the specific resource — "Stockbit's ready-made (guru and preset) screeners" — which distinguishes it from a user-saved list, and the parent_id sentence makes the two listing modes concrete. It never names a sibling tool by name, so differentiation from screener_saved or screener_favorites has to be inferred from the word "ready-made."

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 implied through the two-mode explanation (omit parent_id = list preset groups, set it = list screeners in that group) and the pointer to open one via GET /screener/templates/{id}. There is no explicit when-to-use-this-vs-sibling guidance and no statement of prerequisites or exclusions, leaving the agent to reason about it.

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

Deploy Server

Other Tools