Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Fundamental chart (PE/PBV bands, metric history)

financial_chart
Read-onlyIdempotent

Retrieves historical fundamental metric bands, such as PE or PBV, for one or more companies across a chosen timeframe, helping you analyze valuation trends over time.

Instructions

History of a fundamental metric (e.g. PE or PBV band) for one or more companies over a timeframe, the Fundachart view.

Returns (Stockbit's data field): data[{ratios[{item_id, chart_data[{value, ...}]}]}] - one entry per company; UI takes the last chart_data value

Paywall: unknown.

Endpoint: GET exodus /fundachart.

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": {
      "timeframe": "<timeframe>",
      "companies": "<companies>",
      "item": "<item>"
    },
    "name": "financial_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesComma-separated fitem ids; UI uses '13644,21475' (PER_ID, PBV_ID)
companiesYesComma-separated tickers; UI uses 'IHSG'
timeframeYesRange; UI uses '3y' Default "3y".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: the exact response envelope (data[{ratios[{item_id, chart_data[...]}]}]), the note that the UI takes the last chart_data value, and an explicit 'Paywall: unknown' caveat plus the endpoint.

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 purpose, then return shape, paywall and endpoint in short labelled lines. Slightly technical phrasing ('Returns (Stockbit's data field)') but no wasted sentences.

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 usefully documents the nested return structure and how the UI consumes it, and flags the unknown paywall. For a simple three-parameter read tool this is close to complete, though it omits any note on timeframe formats beyond the schema's '3y' example.

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 all three parameters (item, companies, timeframe) are already documented with UI example values. The description adds no further meaning about parameter syntax or valid values, so the baseline 3 applies.

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?

States a specific verb and resource: history of a fundamental metric (PE/PBV band) for one or more companies over a timeframe, plus the 'Fundachart view' label. It implicitly separates itself from price_chart by saying 'fundamental metric', but never names a sibling explicitly.

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?

Usage is only implied by the phrase 'fundamental metric (e.g. PE or PBV band)' and the Fundachart view reference. There is no explicit when-to-use or when-not-to-use guidance versus price_chart or financial_ratios, so the agent must infer the boundary.

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