Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Comparison metrics

financial_comparison_metrics
Read-onlyIdempotent

Retrieve the financial metrics available in Stockbit's comparison view to identify which data points can be compared across stocks.

Instructions

The metrics the comparison view can show.

Returns (Stockbit's data field): data[{fitem_id, (name), child[{fitem_id, (name)}]}] - group rows with child metric rows

Paywall: unknown.

Endpoint: GET exodus /comparison/metrics.

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

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 this as a safe, read-only, idempotent, open-world operation. The description adds useful context beyond that: the Stockbit response field shape, the grouping of rows into parent and child metrics, an unknown paywall status, and the underlying 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?

The description is compact and front-loads the purpose before the return shape, paywall note, and endpoint. The return notation is terse but structured; the fragmented phrasing is acceptable for an API-style discovery tool.

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 carries the burden of explaining the return shape and does so with the data field and parent/child metric structure. For a zero-parameter read-only discovery endpoint, this is nearly complete, though it could explicitly connect the returned fitem_id values to the comparison call.

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 has zero parameters, so there is no parameter meaning to explain. The baseline for a parameterless tool is 4, and the description appropriately focuses on return structure instead.

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 clearly identifies the resource: the metrics that the comparison view can show. It does not explicitly differentiate this discovery endpoint from the sibling financial_comparison tool, but the purpose is understandable without opening the schema.

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 comparison view can show' and the returned fitem_id fields. There is no explicit instruction to call this first to discover metric IDs before invoking financial_comparison, and no when-not-to-use guidance.

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