Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Comparison peer groups

financial_comparison_industries
Read-onlyIdempotent

Identify the industries and sectors a stock belongs to and retrieve competitor symbols for peer comparison.

Instructions

The peer groups (industries) one symbol can be compared within.

Returns (Stockbit's data field): data{industry[{fitem_id, value}], sector[{fitem_id, value}], competitor[{symbol, ...}]} - competitor[0] is the subject; UI loads competitor[1..2] ratios

Paywall: unknown.

Endpoint: GET exodus /comparison/{symbol}/industries.

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

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, openWorld, non-destructive), so the description is free to add the useful extras: an explicit return shape with the notable rule that competitor[0] is the subject, an explicit 'Paywall: unknown' caveat, and the underlying endpoint. That return-shape disclosure is valuable because no output schema exists.

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 with the resource definition, then returns, paywall, and endpoint in four short blocks with no filler. The dense brace notation is terse but appropriate for a machine-facing contract.

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?

For a single-parameter read tool this covers a lot: return structure, the competitor[0] indexing rule, paywall uncertainty, and the endpoint, which compensates for the missing output schema. It does not address failure/empty-result cases or whether peer lists are cached or symbol-exchange scoped, leaving some operational ambiguity.

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 with an example ('IDX ticker, e.g. BBCA'), so the description adds nothing about parameters. Baseline 3 applies where the schema carries the full parameter burden.

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 identifies the resource concretely — the peer group (industry/sector/competitor) set for one symbol — which is distinct from the sibling financial_comparison/metrics tools that presumably consume those peers. It stops short of an explicit verb and never contrasts itself with financial_comparison, so the boundary is inferable rather than stated.

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 when-to-use or when-not-to-use guidance and no named alternative. The only usage hint is the incidental note that 'UI loads competitor[1..2] ratios', which implies this is a discovery/metadata call rather than the comparison itself, but the agent must infer that.

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