Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Financial items for symbols

financial_ratios
Read-onlyIdempotent

Fetch chosen financial items for one or more stock symbols at once using fitem IDs from screener metrics, returning raw values for ratio and fundamental analysis.

Instructions

Chosen financial items (fitem ids, from screener_metrics) for one or more symbols at once.

Returns (Stockbit's data field): data[{fitem[{value_raw, ...}], ...}] - UI reads data[0].fitem[0].value_raw

Endpoint: GET exodus /findata-view/v1/ratio.

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": {
      "symbols": "<symbols>",
      "fitem_ids": "<fitem_ids>"
    },
    "name": "financial_ratios"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYesTicker(s); UI sends one ('IHSG')
fitem_idsYesFinancial-item id(s); UI sends '21476' (IHSG market cap)

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 cover read-only/idempotent/non-destructive/open-world, so the bar is lower, and the description still adds value: the exact response envelope (data[{fitem[{value_raw,...}]}]) and the fact that the UI reads data[0].fitem[0].value_raw. It also discloses the underlying endpoint. It does not cover batching mechanics or rate limits.

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, front-loaded blocks with no filler: purpose, return shape, endpoint. The 'UI reads data[0].fitem[0].value_raw' clause is cryptic and only tangentially relevant to an agent consumer, but it is brief.

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?

With no output schema, the description does a decent job supplying the return shape and upstream dependency. However, both parameters are typed as a single string while the description claims multi-symbol support, and the description never explains how to pass multiple values — a real gap for correct invocation.

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% with examples already present, so the baseline is 3; the description goes further by stating where valid fitem ids originate (screener_metrics) and that multiple symbols/fitems can be requested at once. It stops short of explaining the delimiter convention for the multi-value string parameters.

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 concrete resource and scope: chosen financial items (fitem ids) for one or more symbols in a single call, and ties fitem ids back to screener_metrics. The verb is implicit ('Returns') and the name 'financial_ratios' is narrower than the 'financial items' framing, but an agent can still tell what it retrieves.

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?

It gives a useful prerequisite — fitem ids come from screener_metrics — which tells the agent to call that sibling first. It does not say when to prefer this over financial_keystats, financial_statements, or financial_comparison_metrics, and there are no exclusions.

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