Skip to main content
Glama

Stock Trends Market Intelligence

Get Stock Trends ST-IM History

stocktrends_get_stim_history
Read-only

Purchase bounded API-authored ST-IM history with an x402 payment authorization. The API data is probabilistic context, not a forecast or recommendation.

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_exchange": "<symbol_exchange>"
    },
    "name": "stocktrends_get_stim_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
limitNo
startNo
include_gapsNo
symbol_exchangeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover read-only/non-destructive behavior, so the bar is low, and the description adds two things not in structured data: this is a paid call gated by x402 payment authorization, and the returned data is probabilistic context rather than a forecast. It omits billing granularity and pagination behavior for large ranges.

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?

Two compact sentences, payment prerequisite and data caveat both front-loaded with no filler. Nothing is padded or repeated.

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

Completeness2/5

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

A paid, range-parameterized history endpoint with no output schema and 0% parameter description coverage needs the description to carry the parameter and return-shape burden, and it does not. Only the payment gate and the data caveat are covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the burden falls entirely on the description, which says nothing about start/end formats, the limit range, include_gaps, or the required symbol_exchange encoding. "Bounded" only faintly gestures at the limit constraints.

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 ("Purchase") and resource ("API-authored ST-IM history"), with the "bounded" qualifier signaling range-limited retrieval. This separates it from stocktrends_get_stim_latest by the history/latest distinction, though "ST-IM" itself is unexplained jargon.

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?

The description discloses a prerequisite (an x402 payment authorization is required to call it) which is real usage guidance, but it never states when to prefer this history endpoint over the sibling "latest" variant or how the range parameters should be chosen. Usage is implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.