Skip to main content
Glama

Market Eyes Live - stock ratings and mortgage-rate context

List the names currently in one tier

list_rated_by_tier
Read-onlyIdempotent

Lists the U.S. stocks in the daily-refreshed rated set whose latest rating carries one conviction tier, strongest composite first: Highest Conviction, Favorable, Hold, Unfavorable, or the speculative and flag words Rising Star, Very Promising, Promising, Runner! and Catalyst Watch. Use this when an agent needs candidates by Market Eyes Live tier, for example 'which names are Highest Conviction today' or 'list the Favorable stocks', to build a watchlist or a scan from the tier rather than from a guess. Each row carries the symbol, company, composite score, as-of date and the public rating page; call check_trade or get_stock_rating on a name for its factors, risks and record. Do not use for quotes, price history, or a personal recommendation. Limitations: the daily-refreshed set only (several hundred names, refreshed through the day), so a ticker scored live on demand is not listed; only ratings dated within five days of the newest one in the set are listed, and the older ones are counted as left out; most funds and REITs carry their own labels in the app and are not listed under these words; up to 25 rows per call; the list is rebuilt at most every 30 minutes. 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": {
      "tier": "<tier>"
    },
    "name": "list_rated_by_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierYesone of: Highest Conviction, Favorable, Hold, Unfavorable, Rising Star, Very Promising, Promising, Runner!, Catalyst Watch
limitNorows to return, strongest first; default 10

Output Schema

NameRequiredDescriptionDefault
noteNo
rowsYes
tierYes
as_ofNothe most recent scoring day in the list
linksNo
sourceYes
list_sizeYeshow many names in the daily-refreshed set carry a current rating (dated within five days of as_of)
disclaimerYes
tier_meaningNowhat the tier word means, in plain words
count_in_tierYeshow many current names in the daily set carry this tier (rows may be fewer)
older_left_outYeshow many names were left out because their latest rating is older than that

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?

Beyond the read-only and idempotent annotations, the description discloses key behavior: only the daily-refreshed set is covered, only ratings within five days of the newest are listed, older ratings are counted as left out, funds and REITs are generally excluded, and results are capped at 25 rows per call and rebuilt at most every 30 minutes. It also identifies the data as research data, read-only, and not financial advice.

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, then usage, alternatives, limitations, and method. It is dense but well organized; there is some repetition of tier labels and ordering already present in the schema, which keeps it from being maximally concise.

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?

For a filtered-list tool with an output schema, this description is complete: it covers scope, tier vocabulary, usage examples, alternatives, exclusions, freshness and row limits, and even the fields each row carries. No material behavioral or contextual gap is apparent.

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 the schema already documents the tier values, limit maximum, minimum, default, and strongest-first ordering. The description enumerates the tier labels and says results are strongest composite first, but this largely repeats structured information rather than adding syntax or format guidance 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?

States a specific verb and resource: lists U.S. stocks in the daily-refreshed rated set by latest conviction tier. It distinguishes the tool from siblings by directing agents to check_trade or get_stock_rating for factors, risks, and records, and explicitly excludes quotes, price history, and personal recommendations.

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?

Gives explicit when-to-use examples such as 'which names are Highest Conviction today' and 'list the Favorable stocks'. It also names alternative tools for per-name details and lists clear out-of-scope uses, leaving little ambiguity about when to call this tool.

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.