Skip to main content
Glama

why_not

Read-onlyIdempotent

Why isn't Coil buying NVDA? Why a name is not a buy today, in plain words: the market gate, a chase, a falling trend, a report coming up or no entry window. The plain reason one stock or ETF is not a candidate today, or the state that makes it one: the market gate for the name's own book and sector, its entry window (READY, SETUP, WAIT, CHASE, FALLING or BASING) and earnings inside five trading days. Not buying is the lesson. 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 symbol 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>"
    },
    "name": "why_not"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. NVDA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the burden is lighter. The description does add real context beyond them: the free tier constraint (one symbol per call, states only, no scores), the morning-read data source, and the shape of the optional 'dip' object. However, it says nothing about the rest of the payload, so an agent still cannot anticipate the main response structure.

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 core idea ('why a name is not a buy today') is restated three times before any new information appears, and the middle of the description degenerates into jargon ('the market gate for the name's own book and sector') and an aphorism ('Not buying is the lesson') that carries no operational meaning. The genuinely useful details, the dip payload and the free-tier limits, are crammed into the final ragged sentences.

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 one-parameter, read-only lookup this is close to sufficient: it names the possible reasons, the entry-window state vocabulary, and the earnings-window rule. But with no output schema, the description should explain the returned fields more fully, and the missing contrast with 'why_not_live' leaves the agent without a selection rule between two near-identical tools.

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% and there is a single, self-evident 'symbol' parameter with its own description and example, so the schema carries the load. The text 'one symbol per call' reinforces the cardinality constraint but adds no format or validation detail. 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 answers a concrete question ('Why isn't Coil buying NVDA?') and enumerates the reasons it returns: market gate, chase, falling trend, upcoming report, no entry window. That is a specific resource with a clear scope. It never distinguishes itself from the sibling 'why_not_live', so an agent cannot tell from the text alone which of the pair to call.

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 statement, no exclusion, and no mention of the obvious alternative 'why_not_live', which sits directly in the sibling list. The only seler information is buried at the end ('from the morning read'), which implies a snapshot rather than live data but never states the trade-off or when the live variant is required.

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