Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Company info and quote header

company_info
Read-onlyIdempotent

Fetch a Stockbit stock page header by ticker for company name, sector, board, price change, tradeability, indexes, and corporate action details.

Instructions

The stock page header of one symbol: name, sector/sub-sector, board, price and change, special notations, indexes it belongs to, tradeability, corporate action banner, day-trade and margin info.

Returns (Stockbit's data field): data{id, name, symbol, symbol_2, symbol_3, display_symbol, exchange, country, type_company ('Saham'|'Waran'|'Right'|...), status ('STATUS_ACTIVE'), tradeable, sector, sub_sector, industry, sub_industry, price, previous, change, percentage, volume, value, average, orderbook{bid{price,volume},offer{...}}, market_hour{status,time_left,formatted_time_left}, tabs[] ('stream','news','keystats','orderbook','analyst','analysis','financials','fundachart','seasonality','chartbit','comparison','corp.action','insider','profile','EPS Estimate'), indexes[], indexes_data[{company_symbol,company_type}], catalogs[{id,catalog_name,company_symbol,parent,company_type,show}], corp_action{active,text,detail}, day…

Endpoint: GET exodus /emitten/{symbol}/info.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker; desktop strips chars outside [a-zA-Z0-9-/] (cleanupValue)
with_sub_industryNoSent as 'true' by the web client (HAR); the desktop bundle sends no query. Populates industry/sub_industry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered by structured data. The description adds the concrete endpoint path and the response envelope shape ('data{...}'), which is genuine context, but says nothing about auth requirements, rate limits, error behavior for invalid symbols, or market-hours-dependent staleness of price fields.

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

Conciseness2/5

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

The opening sentence is well front-loaded, but it is followed by a raw, truncated field dump that cuts off mid-word ('day…'). The enumeration duplicates what a response schema would normally carry and includes noise such as tab keys and catalog field names that an agent cannot act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, describing the return payload is legitimately valuable, and the description covers it broadly. However the dump is incomplete (truncated), mixes nesting levels without structure, and omits any note on how optional fields behave when the symbol is untradeable or the market is closed, so the agent cannot fully predict the response.

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 both parameters (symbol, with_sub_industry) are already documented, including the ticker cleanup rule and the web-vs-desktop quirk. The description contributes nothing about either parameter, so the baseline 3 applies; no additional meaning is layered on top of the schema.

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 names a specific resource and scope: 'the stock page header of one symbol', then enumerates the content it covers (name, sector, board, price, indexes, corporate action banner, day-trade/margin info) and the endpoint it hits. An agent can tell this is a per-symbol quote/header lookup, though it never distinguishes itself from siblings like company_profile, company_indexes, or company_classification, which overlap on sector/index data.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative tool. The agent must infer from the field list that this is the entry-point quote fetch rather than a profile, classification, or index listing. The trailing endpoint string is plumbing, not usage guidance.

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