Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

company_profile

Read-only

Retrieve an IDX ticker's business description and profile data, optionally adding the typed company record or financial line items in the same call.

Instructions

The company description block for a ticker: what the business does, and whatever else Stockbit's profile endpoint carries. Returned verbatim under profile; null there means the endpoint answered with no profile body, which is an answer and not an error. Set include_typed_info or include_fin_items to add the v2 statement-vocabulary views — the typed company record and the financial line items that vocabulary defines. Each is ONE extra upstream request and both are off by default. emitten_type selects that vocabulary and is ignored unless one of those two is requested. "company" is the only value that has been observed; banks and other issuers whose statements differ use another value that is unconfirmed, so an override is accepted but nothing here can tell you it is right — a wrong one is likely to come back as a not_found. Nothing inside profile is parsed. If the body carries percentage- or magnitude-shaped strings — a shareholder block's percentage, a value like "3.24 M" — they are returned as this server received them: not recomputed, not rounded, not cross-checked against each other. Their key names and their units are unconfirmed, and a magnitude suffix is ambiguous on an Indonesian payload (miliar, 1e9, or million, 1e6), so a figure computed from them here would be invented. Treat any percentage there as the upstream's own claim rather than arithmetic this server checked; if you need one, compute it from an unrounded share count and an outstanding-share count, and say that you did. PENDING VERIFICATION: this endpoint has not been observed live.

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. BBRI
emitten_typeNoStatement vocabulary for the v2 views. Default "company"; other values exist but are unconfirmed
include_fin_itemsNoAlso fetch the v2 financial line-item list (one extra request). Default false
include_typed_infoNoAlso fetch the v2 typed company record (one extra request). Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial context beyond that: `null` under `profile` is a valid answer not an error, each include flag costs one extra upstream request, the body is returned unparsed and recomputed nowhere, and the endpoint is flagged PENDING VERIFICATION as never observed live.

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?

Purpose is front-loaded well, but the percentage/magnitude paragraph is long and repeats the same point ('not recomputed, not rounded, not cross-checked' then 'would be invented'), and the PENDING VERIFICATION warning that affects trust in everything above sits at the very end rather than up front.

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 4-parameter read tool with no output schema, the description covers output semantics (verbatim `profile`, null meaning, no parsing or arithmetic done) and the ingestion caveats an agent needs. It stops short of describing the profile block's actual fields, which it explicitly disclaims as unconfirmed — a reasonable boundary, though it leaves the agent unable to plan on the payload shape.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining emitten_type's effect ('selects that vocabulary'), that only 'company' has been observed, and that a wrong override is 'likely to come back as a not_found' — none of which the schema says. The include flags' cost (one extra request each) is also added 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?

The first sentence names a specific resource (the company description block for a ticker) and scopes it to 'what the business does, and whatever else Stockbit's profile endpoint carries.' It is clearly distinct from siblings like quote or ratios, though it never explicitly names an alternative to route away from.

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?

Gives concrete conditional guidance for the optional flags ('set include_typed_info or include_fin_items to add the v2 statement-vocabulary views... both are off by default') and states emitten_type 'is ignored unless one of those two is requested.' It does not state when to prefer this tool over keystats or peer_comparison, but the flag-level usage rules are unusually explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.