Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Login status

session_status
Read-onlyIdempotent

Checks whether Stockbit and trading sessions exist and when they expire, without exposing tokens. Use it to detect missing sessions and tell the user to run the login command.

Instructions

Whether this server has a Stockbit session (needed by every tool) and a trading session (needed by the account_* tools), with their expiry. Never returns the tokens. If a session is missing, tell the user to run stockbit-mcp login (or stockbit-mcp login --trading) in a terminal.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds genuinely new behavioral facts: tokens are never exposed and expiry timestamps are included. It gives no indication of caching, refresh, or how quickly a stale session is reflected, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each doing distinct work: what is reported and its dependency scope first, the privacy guarantee second, the actionable fix third. No filler or restatement of the title.

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 still tells the agent what the response conceptually contains (per-session presence and expiry) and, importantly, what it will not contain (tokens). For a zero-parameter diagnostic this is complete enough to call and to act on.

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 adds nothing parameter-related, but nothing is needed, since the call is fully determined by the tool's name.

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?

The description names the exact resource it reports on (a Stockbit session and a separate trading session) and what it returns (presence plus expiry). It also scopes which tools depend on each session type, so an agent can distinguish this diagnostic from anything data-returning.

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?

It states the conditions that make this tool the right call (checking whether the session prerequisite for all tools, or for account_* tools specifically, is satisfied) and prescribes the exact remediation command when a session is missing. It does not explicitly say when not to use it, but for a diagnostic with no alternatives that is a minor gap.

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