Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

list_alerts

Retrieve every price alert on the account, including ID, symbol, trigger level, active status, message, and last-fired time, to monitor and manage alert conditions.

Instructions

All price alerts on the account: id, symbol, level, active, message, last fired.

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_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does establish that the call is unfiltered and account-wide and that it returns a fixed field set. It says nothing about read-only safety, pagination or ordering, which for a zero-parameter list tool are minor but real gaps.

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?

One short sentence, front-loaded with the resource, followed by the field list, with no filler. Nothing could be removed without losing content.

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?

For a zero-parameter read tool its complexity is near the floor, and the description covers the scope plus the return fields, which partly compensates for the missing output schema. Only ordering and volume expectations are left unstated.

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?

The tool takes no parameters, so the baseline expectation is met; the description correctly implies that filtering is not supported by this call. The enumerated return fields are return-value information rather than parameter semantics, so they do not add parameter meaning but do not detract.

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 definition names the resource and its scope ('All price alerts on the account') and enumerates the fields returned (id, symbol, level, active, message, last fired), so an agent knows exactly what this call yields. It stops short of an explicit verb like 'list' and does not distinguish itself by name from read-adjacent siblings such as list_fires, so it is clear but not fully differentiated.

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 when-to-use guidance and no mention of alternatives: nothing tells the agent to prefer this over create_alert, modify_alert, delete_alert or list_fires, nor does it state prerequisites. The only implicit signal is that it returns all alerts unfiltered, which is a scope statement rather than usage guidance.

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