Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Rights/warrant conversion history

corpaction_conversion
Read-onlyIdempotent

Fetches exercise and conversion history for a warrant or right ticker, including recording dates, conversion counts, remaining shares, and post-conversion stock totals.

Instructions

Exercise and conversion history of a right or warrant (e.g. BUKA-W).

Returns (Stockbit's data field): data{conversion[{company_id, recording_date, conversion_number, remaining_conversion, stock_sum_after_conversion}]}

Endpoint: GET exodus /corpaction/{symbol}/stock_conversion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "corpaction_conversion"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based; next page while conversion[] non-empty Default 1.
limitNolimit Default 50.
symbolYesWarrant/right ticker (e.g. XXXX-W)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuine value beyond that by enumerating the returned conversion fields (company_id, recording_date, conversion_number, remaining_conversion, stock_sum_after_conversion) even though no output schema exists, and by disclosing the backing endpoint.

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 purpose sentence, then return shape, then endpoint — a sensible order with little waste. The raw field-list and endpoint line are slightly technical but earn their place given there is no output schema.

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 simple read-only lookup with three fully documented parameters and no output schema, the description supplies the return structure and the data source, which is what an agent needs. Pagination semantics live in the schema and are adequate there.

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

Parameters3/5

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

Schema description coverage is 100%, so symbol, page, and limit are already documented in the schema itself, establishing a baseline of 3. The description only reinforces symbol with a concrete real-world example (BUKA-W); it adds no other parameter meaning.

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 verb and resource: "Exercise and conversion history of a right or warrant (e.g. BUKA-W)", which is clearly distinct from calendar/status/category siblings. It stops short of explicitly contrasting with those siblings, but the resource is unambiguous.

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 description implies when to use it (querying conversion/exercise history for a specific warrant ticker) but gives no explicit when-not conditions, prerequisites, or named alternatives such as corpaction_status or corpaction_calendar. Usage must be inferred from the resource name.

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