Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

status

Read-only

Check server health, market-data session state, token expiry, IDX clock, and the next command to run when something looks wrong or after login.

Instructions

Is this server working, and what do I run if it is not? Call this FIRST whenever anything looks wrong, and call it after logging in to confirm it took. Reports the version and Node, whether the market-data session is stored (NEVER the token itself), how long the stored market-data token claims it has left, the IDX session clock in WIB, and a nextStep naming the single next command. It answers with no session at all — that is the state every new user is in, and the answer is the useful one. The session also carries a health: ok / failing / expired / not-stored / unknown, derived from what actually happened the last time that credential was used. failing means present and unexpired but REJECTED by Stockbit — revoked, or superseded by another login. That is the case an expiry check cannot see, and it costs no requests. live: true is NOT free and is rarely what you want. It refreshes the market-data token, which ROTATES the refresh-token family and therefore ENDS the user’s Stockbit website session. Use health instead; only pass live: true if the user explicitly asks to prove the token with a real request. The market block reports the IDX clock in WIB with a UTC sibling on each field, and does not model public holidays. server.update says whether a newer release of this server exists. It costs ONE request to the npm registry — not to Stockbit, carrying only the package name — cached for a day and made by this tool alone. isOutdated: true matters: npx caches a resolved tree under a version RANGE, so a user can run a build that is weeks old and nothing else will say so. latest and isOutdated are ABSENT when the check could not run, which means unknown, NOT up to date — read update.note. STOCKBIT_NO_UPDATE_CHECK=1 turns the request off.

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

Input Schema

NameRequiredDescriptionDefault
liveNoProve the market-data token with one real refresh. This ROTATES the token family and ends the user's Stockbit website session — ask them first. Default false; `health` answers the same question for free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive, and the description goes well beyond them: it discloses that the token value is never returned, that `live: true` rotates the refresh-token family and ends the user's Stockbit website session, that the update check costs one npm-registry request cached for a day, and that `isOutdated` is absent when the check fails. It also explains how the `health` enum is derived, which is behavioral context the annotations cannot carry.

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 trigger question and the call-first instruction, and nearly every sentence carries distinct information. It is, however, long for a single-parameter tool, with bold/caps emphasis and a few dense clauses (the npm-registry cost sentence) that could be tightened.

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 output schema, the description carries the full burden and does so: it documents each returned field, the five `health` states including the subtle `failing` case, the absence semantics of `latest`/`isOutdated`, and the env var that disables the update check. An agent has everything needed to call it and to interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single `live` parameter is fully described in the schema, yet the description still adds the consequence the schema only hints at: token-family rotation, ending the user's website session, the 'ask them first' precondition, and the free `health` substitute. This is genuine meaning beyond the structured field.

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?

It opens with a concrete diagnostic question and then enumerates exactly what is returned: version, Node, session stored state, health, IDX clock in WIB, nextStep, and server.update. That is a specific verb+resource framing that cannot be confused with any of the market-data siblings (quote, orderbook, technicals).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states explicit triggers ('Call this FIRST whenever anything looks wrong', 'after logging in to confirm it took') and an explicit exclusion for the one parameter ('live: true is NOT free and is rarely what you want... use health instead'). The alternative path is named and conditioned, leaving nothing to inference.

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