Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Price performance

price_performance
Read-onlyIdempotent

Retrieve a stock symbol's price performance across standard windows—1D, 1W, 1M, 3M, YTD, 1Y, 3Y, and 5Y—to compare returns and track momentum.

Instructions

Return of one symbol over standard windows (1D, 1W, 1M, 3M, YTD, 1Y, 3Y, 5Y).

Returns (Stockbit's data field): data{prices: ...} (only prices is read; element shape unknown).

Endpoint: GET exodus /company-price-feed/price-performance/{symbol}.

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": {
      "symbol": "<symbol>"
    },
    "name": "price_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYessymbol

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful context — the underlying endpoint and the caveat that only `prices` is read with unknown element shape — which honestly warns the agent about data reliability, but return format and pagination remain unstated.

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 sentences with the capability front-loaded and the window list immediately after. The endpoint line is arguably internal implementation detail but is compact and does not bury the core statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the window enumeration effectively describes the returned fields, which is adequate. However, the meaning of each window value (percentage vs. absolute) and the unit/currency are not stated, leaving an agent to guess at the payload semantics.

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?

Only one parameter (`symbol`) exists at 100% schema coverage, so the schema baseline already applies. The description says 'one symbol' but adds no format guidance (ticker suffix, case, exchange prefix) beyond that, so it does not improve on the schema.

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?

States a specific verb and resource ('Return of one symbol') and enumerates the exact windows computed (1D through 5Y), which tells an agent precisely what metric set it gets back. It does not name or contrast any sibling such as price_history or price_chart, so differentiation is inferential rather than explicit.

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 statement of when to use this versus the many price_* siblings, nor any precondition or exclusion. The only usage signal is implied by the enumerated windows, which is weaker than a real routing instruction.

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