Skip to main content
Glama

Market Eyes Live - stock ratings and mortgage-rate context

Check a trade against the rating and its record

check_trade
Read-onlyIdempotent

Checks one U.S.-listed stock or ETF at the moment of a trade: returns the full Market Eyes Live MELANY rating (the same fields as get_stock_rating) together with what the public graded record says about calls carrying that tier: the share of such calls that beat more than half of the other core stocks rated the same day, over the following week and month, with the number of calls behind each figure and the 50% no skill line (a REIT is looked up under the app's own REIT label; an ETF gets no tier figure, because funds are not graded against the same day list, and the record says so). Use this when an agent is about to propose a buy or a sell, for example 'check NVDA before I buy' or 'what does Market Eyes Live say about selling AAPL', so the person approving the trade sees the rating, its tone and its record side by side. The side (buy or sell) only shapes the wording; the rating and the record are the same either way. Do not use for quotes, order placement, options, crypto, futures, non-U.S. listings, or a personal recommendation. Limitations: the daily-refreshed set answers instantly, other covered tickers are scored live at a lower hourly limit; the record is read from the public feed at https://marketeyeslive.com/api/validation-status and is left out, with a note, when that feed cannot be read in time; it does not return any trade plan values. Method: https://marketeyeslive.com/how-melany-is-tested.html. Research data, not financial advice; this tool is read-only and never places trades.

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

Input Schema

NameRequiredDescriptionDefault
sideNooptional: the trade being considered; it changes the wording only
symbolYesU.S. ticker symbol, e.g. NVDA, AAPL, VOO

Output Schema

NameRequiredDescriptionDefault
readYesthe rating in one sentence and its tone
sideNobuy or sell, when given
as_ofYesYYYY-MM-DD scoring date
linksNo
scaleNo
themeNo
recordYesWhat the public graded record says about calls carrying this tier: the share that beat more than half of the other core stocks rated the same day, over each window. 50% is the no skill line. Present on every success; available is false when the feed could not be read in time.
sourceYesdata source name
symbolYes
companyNo
factorsYeseach 0-100, higher is stronger
freshnessNopresent only when scored live on demand
top_risksNodescriptive risk notes; never instructions
disclaimerYes
trade_planNoPresent only when Market Eyes Live has a trade plan for this ticker (including a suggested entry zone and a model position size; the same plan for every reader, not based on anyone's account, holdings or finances). The plan values are never included here; they are part of a Market Eyes Live subscription.
asset_classNostock, etf or reit: which label table the eight factor slots carry (a fund's quality slot is cost and structure, a REIT's valuation slot is price against funds from operations)
rating_tierNoConviction tier. Mature ladder, weakest to strongest: Unfavorable, Hold, Favorable, Highest Conviction. Favorable and Highest Conviction are both favorable reads; Highest Conviction is a composite of 69 or above (for a stock, a small hysteresis can hold a borderline label steady between refreshes; a fund or REIT word follows its label in the app, which has none). Names the mature ladder does not cover carry their own label: Promising, then Very Promising, then Rising Star for names without mature fundamentals, Runner! for a momentum surge, Catalyst Watch for a news-driven gap up on volume. ETFs and REITs use the same mature ladder, chosen by the tone of the fund's own label in the app (a favorable fund label reads Favorable or Highest Conviction, a cautious or neutral one Hold, a negative one Unfavorable); a leveraged or inverse fund never reads above Hold. These nine words are the complete set; null when no tier applies.
composite_scoreYes0-100, higher is stronger

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only, open-world, idempotent, non-destructive annotations, the description discloses limits and failure behavior: the daily-refreshed set answers instantly while other covered tickers are scored live at a lower hourly limit, and the public record feed is omitted with a note when unavailable. It also clarifies that the side only affects wording and that no trade plan values are returned.

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?

The description is front-loaded with purpose and usage, and nearly every sentence carries useful information. It is longer than necessary in one dense paragraph, with parentheticals and repeated disclaimers that could be tightened, but the structure remains understandable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema already exists, the description need not define return values in full, yet it still explains the rating fields, record fields, sample sizes, the 50% no-skill line, and failure behavior. It is complete for a read-only two-parameter lookup tool with an output schema.

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

Parameters5/5

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

Schema coverage is complete, but the description still adds meaning: side changes only the wording and not the rating or record, symbol accepts a U.S. ticker, REITs are looked up under the app's REIT label, and ETFs get no tier figure because funds are not graded against the same-day list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it checks one U.S.-listed stock or ETF at trade time and returns the MELANY rating plus the graded record for that tier. It explicitly distinguishes the return from get_stock_rating by saying it includes the same rating fields together with record data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger: use when an agent is about to propose a buy or sell, with concrete examples such as checking NVDA before buying or AAPL before selling. It also lists clear exclusions: quotes, order placement, options, crypto, futures, non-U.S. listings, and personal recommendations.

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.