Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Rights and warrant exercises

account_exercises
Read-onlyIdempotent

Fetch rights and warrants exercise requests from Stockbit using your trading session, returning IDR amounts and 100-share lots for corporate action tracking.

Instructions

Exercise requests of rights and warrants.

Needs the trading session (stockbit-mcp login --trading). Values IDR; lots of 100 shares.

Returns (Stockbit's data field): {data:[...]} exercise requests (fields not transcribed).

Endpoint: GET carina /exercise.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds meaningful context beyond them: an authentication/session prerequisite, that values are in IDR, that quantities are in lots of 100 shares, and the shape of the returned data field.

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?

Short, front-loaded sentences covering purpose, prerequisite, units, return shape and endpoint with no filler. The phrasing is slightly telegraphic ('fields not transcribed'), but nothing is redundant.

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?

For a zero-parameter, read-only listing with no output schema, the description covers purpose, auth prerequisite, units and the top-level return shape. It openly notes that individual fields are not transcribed, which is a minor but acknowledged gap.

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?

There are zero parameters, so the baseline is 4. The description still clarifies the units of the returned data (IDR, lots of 100 shares), which adds interpretive value even though there is no input schema to elaborate on.

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 states a specific verb and resource: listing exercise requests of rights and warrants, and names the underlying endpoint (GET carina /exercise). It is clearly distinguishable from the sibling account_* tools, though it does not explicitly contrast itself with any of them.

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?

It gives a prerequisite ('Needs the trading session (stockbit-mcp login --trading)'), which implies when the tool will succeed, but it offers no when-to-use/when-not guidance or named alternatives for retrieving exercise data.

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