Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Company profile

company_profile
Read-onlyIdempotent

Retrieves a company's profile, including business description, listing date, address, management, shareholders, and corporate history using its IDX ticker.

Instructions

Business description, listing date, address, management (board of directors and commissioners), shareholders and the history of the company.

Returns (Stockbit's data field): data{background, address[], history{date, board, price, shares, amount, free_float, registrar, administrative_bureau, underwriters[]}, key_executive{president_director[], director[], vice_president[], president_commissioner[], vice_president_commissioner[], commissioner[], independent_commissioner[], independent_president_commissioner[], independent_vice_president_commissioner[]}, shareholder[], shareholder_director_commissioner[{...,percentage}], shareholder_one_percent{shareholder[], last_updated}, beneficiary[], shareholder_numbers[{shareholder_date, total_share, change_value (int64 as string; client BigInt()s it), change_formatted}]}

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

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBCA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description is free to add the genuinely missing piece: the shape of the returned payload, including nested history, executive, and shareholder groups. That is real value beyond the structured fields, though it omits auth requirements, error behavior for unknown symbols, and notes that change_value is stringified int64 for BigInt handling only in passing.

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

Conciseness3/5

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

The first sentence is well front-loaded, but the return-value block is a dense, comma-heavy dump that is hard to scan and would be better as a structured list. It earns its place given no output schema exists, but the presentation is clumsy.

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?

With no output schema, the description must carry the return contract, and it does enumerate the major payload branches including nested shareholder_director_commissioner and shareholder_one_percent. It is close to complete for a read-only fetch, with minor gaps around failure modes and market coverage.

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 coverage is 100% and the single symbol parameter is already documented as an IDX ticker with example BBCA. The description only echoes {symbol} in the endpoint path, adding no new meaning, which is the expected baseline for a fully documented single parameter.

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 the concrete resource contents (business description, listing date, address, board, commissioners, shareholders, history) and the endpoint that serves them, so an agent knows this retrieves a listed company's profile by ticker. It does not explicitly contrast itself with close siblings such as company_info or company_subsidiaries, so differentiation is left to the reader.

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 statement of when to call this versus the many other company_* tools; the only routing signal is the content list itself. No prerequisites, no exclusions, and no mention that the symbol must be an IDX ticker (that clue lives only in the schema).

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