Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

list_fires

Retrieve fired TradingView price alerts in newest-first order, including each alert's fire time and message, to review recent alert history.

Instructions

Alerts that have fired, newest first, with fire time and message.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses sort order ('newest first') and partial return fields ('fire time and message'), but omits whether the operation is read-only, pagination/truncation behavior, and permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single compact sentence with no wasted words, front-loading the resource and key behavioral traits. Every element earns its place, though it could be expanded for clarity without harming conciseness.

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 simple one-parameter list tool with no output schema, the description gives a useful glimpse of return ordering and fields. However, it omits parameter semantics, sibling differentiation from 'list_alerts', and operational details such as whether results are capped or paginated.

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?

The one parameter 'limit' has 0% schema description coverage, and the description does not mention it at all. It therefore adds no meaning about the parameter's purpose, default, or maximum value, failing to compensate for the missing schema documentation.

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 specifies the resource ('Alerts that have fired') and return content ('fire time and message') with ordering ('newest first'), so an agent can understand what is listed. It does not explicitly differentiate from the sibling 'list_alerts', leaving ambiguity between active alerts and fired alert history.

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 when-to-use guidance, no mention of alternatives such as 'list_alerts', and no exclusions or prerequisites. The distinction between listing all alerts and listing fired alerts is implied only by the word 'fired'.

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