Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

find_pivots

Detects swing highs and lows from the last N candles of a chosen timeframe, returning exact candle times and prices for chart analysis.

Instructions

Swing highs and lows with exact candle times and prices, from the last N candles of a timeframe.

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

Input Schema

NameRequiredDescriptionDefault
countNo
strengthNo
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return content (swing highs/lows with times and prices) and scope (last N candles), but omits how pivots are detected, what 'strength' controls, whether the operation is read-only, and what happens when no pivots are found.

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 single sentence is front-loaded and free of filler. It is efficient, though its terseness contributes to the missing parameter and behavioral detail.

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?

For a tool with three undocumented parameters, no annotations, and no output schema, the description is too thin. It should at minimum explain strength, resolution format, and the shape of the returned pivot data.

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%, so the description must explain all three parameters. It maps 'N' to count and 'timeframe' to resolution, but never explains the 'strength' parameter or any accepted resolution format, leaving a significant gap.

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 clearly states the resource: swing highs and lows with exact candle times and prices, scoped to the last N candles of a timeframe. It is specific enough to distinguish pivot detection from candle retrieval or drawing tools, though it does not explicitly name a sibling alternative.

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 explicit guidance on when to use this tool versus alternatives such as get_candles or chart_health. Usage is only implied by the phrase 'from the last N candles of a timeframe,' with no exclusions or prerequisites.

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