Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Screener metrics

screener_metrics
Read-onlyIdempotent

Retrieves the authoritative tree of metrics a Stockbit screener rule can use, with each fitem_id needed by screener_run. Use it to pick selectable fields like Price, RSI, or PE before building a rule.

Instructions

The tree of metrics a screener rule can use, with their fitem ids (needed by screener_run).

Returns (Stockbit's data field): data[{fitem_id, fitem_name, child[{fitem_id, fitem_name, child[{fitem_id, fitem_name, child[]}]}]}] - a node with empty child[] is selectable; its fitem_id goes into rule.item1/item2. This is the authoritative metric vocabulary (names such as 'Price', 'Price MA 20', 'RSI (14)', 'MACD (12,26)', 'Bandar Accum/Dist', 'Net Foreign Buy / Sell', 'Current PE Ratio (TTM)', 'Piotroski F-Score' per the user's notes).

Paywall: unknown.

Endpoint: GET exodus /screener/metric.

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": "screener_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered; the description adds the full return shape (nested fitem_id/fitem_name/child tree), the selectability rule (empty child[] means selectable), and the 'Paywall: unknown' caveat plus the endpoint. That is meaningful behavioral context, though the paywall note is a flag rather than a resolution.

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 the purpose, then the return shape, then the usage rule and caveats; the nested-bracket notation is compact. Minor waste: the long parenthetical list of example metric names and the 'per the user's notes' attribution add bulk without changing how the tool is called.

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?

There is no output schema, so the description must carry the return contract — and it does, specifying the exact nested structure and how to identify selectable leaves. Combined with the dependency on screener_run and the paywall caveat, an agent has everything needed to call it and use the result.

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?

The tool takes zero parameters, so the baseline is 4. The description instead spends its effort explaining how the returned fitem_id maps into rule.item1/item2 on screener_run, which is genuinely useful downstream semantics.

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 resource (the tree of metrics a screener rule can use) and its role: supplying fitem ids consumed by screener_run. That immediately separates it from siblings like screener_run, screener_presets, and screener_universe, which operate on rules or universes rather than the metric vocabulary.

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 description makes the workflow dependency explicit ('with their fitem ids (needed by screener_run)'), so an agent knows to call this before building or running a rule. It stops short of naming when-not-to-use conditions or alternative vocabulary sources, but the sequencing guidance is clear.

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