Skip to main content
Glama

check_my_trade

Read-onlyIdempotent

Is my trade sound? Your own trade, held against the desk's principles before it is placed: a named stop below the entry, the stop distance, the name's entry state, a report inside the hold and the market gate. Applies Coil's published principles to a long trade the caller proposes in a US stock or ETF, from three numbers: the symbol, the entry and the stop. Returns a verdict of consistent, wait or pass with every reason: the stop's distance as a percentage of the entry, whether the name's state makes the entry a chase, a report inside five trading days and the market gate for the name's book. Impersonal: it reads only the numbers given and never an account. dip: {ok, codes, setup}: present only for oversold-pullback candidates; a dip buy only on a completed hourly turn above the entry-quality and depth floors. Free: one name per call, states only and no scores, from the morning read.

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>",
      "entry": "<entry>",
      "stop": "<stop>"
    },
    "name": "check_my_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopYesThe stop price: the level at which the trade is wrong, below the entry, e.g. 51.50
entryYesThe planned entry price, e.g. 54.20
symbolYesTicker, e.g. NVDA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely new behavior: it is impersonal, reads only the supplied numbers and never an account, is free, handles one name per call, returns states rather than scores, and includes a conditional 'dip' block only for oversold-pullback candidates. It never contradicts the annotations. What it omits is failure behavior, e.g. what happens if the stop is above the entry or the symbol is unknown.

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

Conciseness2/5

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

The opening rhetorical question ('Is my trade sound?') and the near-duplicate framing of 'the desk's principles' versus 'Coil's published principles' spend words without adding meaning. The final sentence stringing together 'dip: {ok, codes, setup}', 'entry-quality and depth floors' and 'the morning read' packs undefined jargon into a dense run-on, so the paragraph is not front-loaded and is harder to parse than its content requires.

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?

With no output schema, the description does a fair job of sketching the return shape (verdict plus reasons plus an optional dip object), and it notes the free/one-name/no-account constraints. However, key concepts it relies on, such as 'market gate', 'entry-quality and depth floors' and 'a report inside five trading days', are left undefined, and the relationship to check_my_trade_live is only hinted at.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all three parameters including the constraint that the stop sits below the entry. The description restates 'the symbol, the entry and the stop' and adds only the framing that the stop is 'a named stop below the entry', which the schema already covers. Baseline 3 is appropriate.

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 names a specific verb and resource: it evaluates a proposed long trade in a US stock or ETF from three inputs (symbol, entry, stop) and returns a verdict of consistent/wait/pass through a named list of criteria (stop distance, chase state, report timing, market gate). The closing phrase 'from the morning read' implicitly separates it from check_my_trade_live without ever naming that sibling, which keeps it short of a 5.

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 context is implied rather than stated: it applies to 'a long trade the caller proposes' before it is placed, is limited to 'one name per call', and covers 'states only and no scores'. There is no explicit when-not guidance and no naming of the obvious alternatives (check_my_trade_live, why_not) to route the agent between them.

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