Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Search the Stockbit endpoint catalog

api_catalog
Read-onlyIdempotent

Find Stockbit endpoints for api_get and look up exact parameter enums by listing available API paths, allowed values, and response shapes; filter by group or query.

Instructions

Lists Stockbit endpoints the desktop app uses, with their parameters, allowed values and what they return. Use it to find an endpoint for api_get when no dedicated tool fits, or to look up the exact enum values a dedicated tool accepts. Filters combine; with none, it lists groups and counts only.

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

Input Schema

NameRequiredDescriptionDefault
groupNoExact group, e.g. market, emitten, insider, screener, trading.
limitNoMax endpoints to return, default 20.
queryNoWords matched against id, path, group and feature (all must match), e.g. "broker summary".
include_writesNoAlso list endpoints that change something (for reference; api_get only reads).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and non-destructive, so the safety profile is covered. The description adds the unfiltered-call behavior (groups and counts only) and notes in the schema that write endpoints are listed for reference only since api_get reads — genuinely useful context beyond the annotations. Pagination beyond the limit cap is not discussed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: what it returns, when to use it versus alternatives, then the filter/default behavior. Front-loaded and free of restatement or filler.

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?

For a read-only, 4-parameter discovery tool with full schema coverage and no output schema, the definition covers purpose, alternatives, filter combination, and the no-filter default. The only gap is that it never says whether the returned parameter metadata is sufficient to construct a valid api_get call, which an agent must know before chaining the two tools.

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%, so baseline is 3, but the description adds real semantics the schema does not: 'Filters combine' (AND semantics across group/query/limit/include_writes) and the zero-filter default that returns groups and counts instead of endpoint rows. Both materially change how an agent constructs a call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists Stockbit endpoints the desktop app uses') and enumerates the payload ('parameters, allowed values and what they return'). It also names its consumer, api_get, so an agent can place it relative to the dedicated per-endpoint tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives two explicit use cases — find an endpoint for api_get when no dedicated tool fits, or look up exact enum values a dedicated tool accepts — which covers both the discovery and clarification paths and implies dedicated tools are the first choice.

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