Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Companies in an index or catalog

company_by_catalog
Read-onlyIdempotent

Fetch the companies that belong to a specific index or catalog using its catalog code (e.g., LQ45) to obtain the constituent list for analysis.

Instructions

Members of an index or catalog (e.g. LQ45) by its catalog code.

Returns (Stockbit's data field): data{companies[...same row shape as subsector companies...]}

Endpoint: GET exodus /emitten/catalog/{catalogCode}/company.

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": {
      "catalogCode": "<catalogCode>"
    },
    "name": "company_by_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
catalogCodeYescatalog_code from v2 info catalogs (e.g. ETF catalogs)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuine value beyond that by disclosing the response shape (data.companies with a row shape matching subsector companies) and the underlying endpoint, but says nothing about pagination, result size, or what happens with an invalid catalogCode.

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 blocks with the purpose front-loaded, no filler sentences. The endpoint line and the parenthetical '...same row shape as subsector companies...' are slightly cryptic but each carries information rather than padding.

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 single-parameter read with no output schema, the description covers purpose, parameter origin, example value, and the shape of the returned data, which is enough for an agent to call it correctly. Missing only edge-case behavior and cross-references to sibling classification tools.

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 coverage is 100% and the schema property already explains that catalogCode comes from 'catalog_code from v2 info catalogs'. The description reinforces this with the LQ45 example and the URL path template, but adds no syntax, format, or validity details beyond what the schema provides, so 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?

The description uses a concrete verb-object framing ('Members of an index or catalog ... by its catalog code') and gives a real example (LQ45), so the agent knows this returns constituent companies rather than the catalog list itself. It also references a row shape shared with 'subsector companies', implicitly distinguishing it from that sibling, but it never names an alternative tool 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: the agent can infer 'call this when you have a catalog/index code and want its members.' There is no when-not guidance and no mention of the closely related siblings (company_by_classification, company_by_subsector, company_indexes), which is a real gap given the dense sibling set.

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