Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Screener universes

screener_universe
Read-onlyIdempotent

Lists available stock universes—IHSG, indexes, sectors, and watchlists—so you can choose the right universe for a Stockbit screener query.

Instructions

The stock universes a screener can run on: IHSG, indexes, sectors, watchlists.

Returns (Stockbit's data field): data{index[{id, name, scope?, list[{id, name, scope?}]}], sectors[{id, name, subsector[{id, name}]}], watchlist[{id, name}]} - chosen option is serialized into the run body's universe string

Paywall: unknown.

Endpoint: GET exodus /screener/universe.

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_universe"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuine value beyond that: the full shape of the returned data groups, the note that a chosen option feeds the run body's universe string, and an explicit 'Paywall: unknown' disclosure. The endpoint notation is low-value but harmless.

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 sentence, followed by the return structure, paywall note and endpoint. The field-by-field return dump is dense but earns its place given there is no output schema. Minor waste in the trailing 'Endpoint: GET exodus /screener/universe.' line.

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?

With no input parameters and no output schema, the description carries the burden of describing return values, and it does so thoroughly, down to the index/sector/watchlist nesting. It also flags the one unknown (paywall) rather than omitting it, leaving no material gap for an agent.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless call whose output is a fixed catalog of options.

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 resource and its contents: 'The stock universes a screener can run on: IHSG, indexes, sectors, watchlists.' The verb is implicit (this is a listing tool), but the enumeration of universe types makes the scope concrete and distinguishable from sibling tools like screener_metrics or screener_presets. It stops short of explicitly naming which sibling it complements.

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?

The line 'chosen option is serialized into the run body's universe string' implies the intended workflow: call this to pick a universe before running a screener. However, it never explicitly says when to call it versus screener_presets or screener_favorites, nor does it state prerequisites or ordering.

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