Skip to main content
Glama

Pre-Flight check link

preflight_link
Read-only

A link that opens SignalStates Pre-Flight with a planned trade filled in; it checks the stop against normal noise, liquidation, holding cost, crowding and size.

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>",
      "side": "<side>"
    },
    "name": "preflight_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
stopNo
entryNo
symbolYesCoin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).
targetNo
leverageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It does add the analytical scope of the check, which is genuinely useful. However, it says the link 'checks' the trade without clarifying that this tool merely constructs a URL rather than performing the analysis or returning a verdict, which leaves an ambiguity for the agent.

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?

It is a single compact sentence, front-loaded with what the tool produces, and every clause adds information about the check's scope. The trailing enumeration of five check dimensions is slightly dense but not wasted wording.

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 6-parameter tool with 17% schema coverage and no output schema, the definition leaves too much out: the format of the returned link, whether optional params can be omitted and what happens then, and whether the result is a URL string or a rendered check. The behavioral scope is described, but the operational details an agent needs to call it correctly are missing.

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 only 17% — only symbol is documented, while side, entry, stop, target and leverage carry no descriptions at all. The description mentions no parameter by name and gives no meaning to the optional fields or how they interact (e.g. whether stop or target default when omitted). With coverage this low, the description should compensate, and it does not.

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 states concretely that the tool returns a link that opens SignalStates Pre-Flight with a planned trade pre-filled, and lists the dimensions the check covers (stop vs. noise, liquidation, holding cost, crowding, size). That is a specific resource plus a specific output kind, so an agent can tell what it produces. It stops short of differentiating itself from the close sibling position_size, which covers related sizing analysis.

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?

Usage is only implied: an agent can infer it is for validating a planned trade before entry, but there is no explicit when-to-use statement, no when-not-to-use, and no routing to alternatives such as position_size or liquidation_price. The scenario is guessable from 'planned trade' but never spelled out.

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.

Resources