Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Indexes

company_indexes
Read-onlyIdempotent

Retrieve latest values and percentage changes for Indonesian stock market indexes like IHSG, LQ45, and sector indexes.

Instructions

IDX indexes (IHSG, LQ45, IDX30, sector indexes …) with their latest value and change.

Returns (Stockbit's data field): data{main[], all[]} - UI concatenates main+all; items {id, symbol, last, change, percent}

Endpoint: GET exodus /emitten/indexes/mobile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "company_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. Beyond that, the description discloses the return envelope (data.main[] and data.all[]) and the non-obvious consumption rule that the UI concatenates main+all, which is genuinely useful behavioral context an agent could not derive from annotations or schema.

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?

Three short sentences, front-loaded with the resource and the returned fields, followed by the payload shape and the endpoint. The endpoint string and the '(Stockbit's data field)' phrasing are somewhat internal-facing, but they are compact and not padded.

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 zero parameters and no output schema, the description carries the burden of explaining returns and does so by enumerating the item fields (id, symbol, last, change, percent) and the two-array envelope. That is sufficient to consume the response correctly; only an explicit usage condition against sibling tools is missing.

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?

The tool takes no parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly avoids inventing inputs and instead spends its space on output shape.

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 (IDX indexes such as IHSG, LQ45, IDX30, sector indexes) and states what is returned about it (latest value and change), so an agent immediately knows this is an index-quote lookup rather than a company lookup. It does not explicitly contrast itself with the company_* siblings, but the resource divergence is obvious from the concrete examples.

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?

No explicit when-to-use or when-not-to-use statement and no named alternative is given. Usage is only implied by the enumerated index families, which tells the agent the scope of the data but not the conditions under which this tool is the right choice versus other market-data tools.

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