Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Search

search
Read-onlyIdempotent

Find companies and insiders by ticker or name, returning matching Stockbit IDs, company names, and icons for further market data lookups.

Instructions

Searches companies (and people/insiders) by ticker or name.

Returns (Stockbit's data field): data{companies[{company_id, name (ticker), desc (company name), icon_url}], insiders[{id, label}]}

Endpoint: GET exodus /search/v2.

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": {
      "keyword": "<keyword>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo0-based Default 0.
typeNoRepeated key (paramsSerializer indexes:null => type=A&type=B)
limitNolimit Default 10.
keywordYeskeyword
insider_categoryNoRepeated key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that by documenting the response envelope (data.companies and data.insiders field names) and the backing endpoint. It does not mention pagination behavior or how type/insider_category filter the results.

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 lines: purpose first, then the return shape, then the endpoint. It is front-loaded and wastes no words, though the return-shape line is dense enough that it reads more like a schema dump than prose.

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's return-field documentation is genuinely necessary and is supplied here. Combined with the endpoint and 100% schema coverage on inputs, an agent has enough to call it correctly; only filtering semantics and pagination defaults are left implicit.

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%, so the schema already documents page, limit, type and insider_category. The description only adds the meaning that the keyword may be a ticker or a company name, which is useful but minimal; it says nothing about how the array-typed filters behave.

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 gives a specific verb and resource ('Searches companies (and people/insiders)') and states the lookup key ('by ticker or name'), which is far more informative than the bare name 'Search'. It does not explicitly differentiate itself from sibling tools, but an agent can tell this is a symbol/entity lookup rather than an account or alert operation.

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?

There is no when-to-use / when-not-to-use guidance and no named alternative for lookup tasks. The only directional signal is the parenthetical that insiders are included, which implies scope but does not tell the agent when to prefer this over other discovery 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