Skip to main content
Glama

Market Eyes Live - stock ratings and mortgage-rate context

Explain a rating in plain words

explain_rating
Read-onlyIdempotent

Returns the Market Eyes Live MELANY rating for one U.S.-listed stock or ETF (every get_stock_rating field) with an explanation a first time investor can follow: what the tier word means, how to read the 0 to 100 composite, and for each of the eight factors its label, what it measures and what its score reads as (strong, leaning strong, middle, leaning weak or weak), on the label table for the asset class (a fund's quality slot is cost and structure, a REIT's valuation slot is price against funds from operations). Use this when the person wants the rating explained rather than just stated, for example 'explain the Market Eyes Live rating on MSFT' or 'what do these factor scores mean'. Do not use for quotes, options, crypto, 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 explanations describe the numbers and never say what to do; it does not return any trade plan values. Method: https://marketeyeslive.com/how-melany-is-tested.html. Research data, not financial advice; read-only, 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": "explain_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesU.S. ticker symbol, e.g. NVDA, AAPL, VOO

Output Schema

NameRequiredDescriptionDefault
as_ofYesYYYY-MM-DD scoring date
linksNo
scaleNo
themeNo
sourceYesdata source name
symbolYes
companyNo
factorsYeseach 0-100, higher is stronger
explainedYes
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.6/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds meaningful behavioral detail beyond them. It explains the daily-refreshed fast path versus live scoring at a lower hourly limit, clarifies that explanations never say what to do, and notes that it returns no trade plan values.

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 the core return value and then proceeds through usage, exclusions, and limitations in a logical order. It is dense but mostly earns its length; there is minor repetition around read-only behavior and financial-advice disclaimers.

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 that an output schema exists, the description does not need to explain return values in detail. It still supplies enough context about the explanation content, factor labels, limitations, and exclusions for an agent to call the tool correctly.

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 description coverage is 100%, so the single symbol parameter is already documented well. The description adds scope context by saying the symbol must be a U.S.-listed stock or ETF, but it does not add syntax or format meaning beyond the schema.

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 returns the MELANY rating for one U.S.-listed stock or ETF with an explanation. It also clearly distinguishes the explanation-oriented use case from merely stating a rating, which is the key contrast with get_stock_rating.

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 explicit when-to-use guidance with examples like 'explain the Market Eyes Live rating on MSFT' and 'what do these factor scores mean'. It also gives explicit exclusions for quotes, options, crypto, 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.