Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Sector overview

company_sectors
Read-onlyIdempotent

Retrieve sector average price changes to detect sector rotation and obtain sub-catalog IDs for drilling into subsector companies.

Instructions

Sectors with their average change, to see sector rotation.

Returns (Stockbit's data field): data{pchange_info[{id, symbol, symbol_2, icon, percent, change}]} - id is the sub-catalog id passed to /emitten/v3/sector/70/subsector/{id}/company

Endpoint: GET exodus /emitten/company/catalog.

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

Input Schema

NameRequiredDescriptionDefault
sortbyNoHard-coded 'pchange' by the UI Default "pchange".
set_priceNoHard-coded 1 by the UI (include price change) Default 1.

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 declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds value by spelling out the exact response envelope (data.pchange_info fields) and the underlying endpoint. The note that 'id' is the sub-catalog id consumed by /emitten/v3/sector/70/subsector/{id}/company is real chaining context an agent could not infer from annotations alone.

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 purpose is front-loaded in the first sentence and the payload/endpoint detail follows compactly. The return-spec sentence is a dense run-on with a raw URL-like path, but every element carries information rather than 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?

There is no output schema, so the description's explicit return-field listing is exactly the missing piece and it supplies it, plus the endpoint path. The only gap is that it says nothing about the semantics of the returned percent/change values (units, baseline) or result ordering.

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 description coverage is 100% and both parameters (sortby, set_price) are documented there as UI hard-coded defaults. The description adds nothing about them, so the baseline 3 for fully covered schemas 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 opening clause names a specific resource and metric ('Sectors with their average change') and gives the analytical intent ('to see sector rotation'), which is far more than a restatement of the name. It does not explicitly distinguish itself from the nearby company_subsectors or company_by_classification siblings, so it stops short of a 5.

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 through the phrase 'to see sector rotation' and the note that the returned id feeds the subsector company endpoint, which hints at a drill-down workflow. There is no explicit statement of when to prefer this over company_subsectors or company_classification, and 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