Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Peer comparison

financial_comparison
Read-onlyIdempotent

Compare a stock's financial ratios with its industry peers to assess relative valuation and performance. Provide a symbol to retrieve peer comparison data.

Instructions

Ratios of one symbol next to its industry peers (the Comparison tab).

Returns (Stockbit's data field): data{symbol, data_value[{fitem_id, value ('N/A' when missing)}]}

Paywall: unknown.

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

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

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBCA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds real value beyond them: the exact return shape, the sentinel 'N/A' for missing values, and an explicit 'Paywall: unknown' caveat. The endpoint disclosure aids debugging but is minor.

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-loads the core purpose in the first sentence, then supplies return shape and metadata in short labeled lines. Slightly fragmented but every line carries information.

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?

No output schema exists, but the description compensates by spelling out the returned data structure including the 'N/A' sentinel. Remaining gaps (what fitem_id identifiers map to, which ratios are included) are modest for a single-parameter read tool.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself giving the 'IDX ticker, e.g. BBCA' example. The description adds nothing further about the symbol parameter, so the baseline of 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 resource ('Ratios of one symbol next to its industry peers') plus the source tab, which tells an agent this is peer-relative ratio data. It does not differentiate from siblings like financial_comparison_metrics or financial_comparison_industries, so the boundary is left implicit.

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?

No when-to-use, when-not-to-use, or prerequisite guidance is given; the only contextual cue is the parenthetical '(the Comparison tab)'. An agent must guess how this differs from the other comparison 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