Skip to main content
Glama
cse-mcp

cse-mcp

Today's trades by price

get_trades_by_price
Read-onlyIdempotent

Retrieve today's trades for a stock grouped by price level, showing shares, trade counts, and VWAP to reveal where buying and selling occurred.

Instructions

Today's trading in one stock broken down by price level: how many shares and trades went through at each price, plus the volume-weighted average price (VWAP). Useful for spotting where the real buying/selling happened.

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

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds real value by naming the aggregate contents (per-price share/trade counts plus VWAP), though it says nothing about limits on price levels returned or behavior for symbols that didn't trade today.

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 sentences, front-loaded with the core breakdown and followed by the analytical purpose; nothing is redundant. The closing clause is mildly promotional but still conveys intent.

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?

An output schema exists, so return-value detail is not required, and for a single-parameter read tool the description covers scope and payload shape adequately. Minor gaps remain around timezone/market-session definition of 'today' and alongside which markets symbols are accepted.

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

Parameters4/5

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

Only one parameter exists and the schema documents it by name only (0% coverage), so the description carries the burden. It clarifies that exactly one stock is in scope, which is the main semantic risk for a symbol argument, even if it does not spell out ticker format or exchange qualification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource with a precise scope: today's trading in one stock broken down by price level, returning shares, trade counts per price, and VWAP. The 'today's' qualifier cleanly separates it from a historical sibling like get_price_history.

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?

Offers an implied use case ('useful for spotting where the real buying/selling happened') but never states when to pick this over get_price_history or get_market_daily_summary, nor any prerequisites such as market hours or symbol validity.

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