Skip to main content
Glama

mkts Market Data

by io.mkts
OverviewDiscussionsAdmin

Screen assets

screen_assets
Read-onlyIdempotent

Find assets matching price, daily-move, volume, market-cap, asset-type and sector filters, sorted as requested. Use for questions like "biggest movers today", "tech stocks over $1T" or "cheapest crypto by price"; all filters are optional and combine with AND. Covers the whole mkts universe (stocks, ETFs, crypto, commodities, forex) from the snapshot, which refreshes about every 15 minutes. Returns at most 25 assets. For valuation or profitability filters such as P/E or margins, this tool does not apply; fetch fundamentals for specific symbols with get_fundamentals.

Input Schema

NameRequiredDescriptionDefault
sortNoField to rank by. Use change24h with direction desc for top gainers, asc for top losers.marketCap
typeNoOnly this asset class.
limitNoMaximum assets to return.
sectorNoStocks and ETFs only; exact name, case-insensitive: Technology, Healthcare, Financial Services, Consumer Cyclical, Consumer Defensive, Communication Services, Industrials, Energy, Basic Materials, Real Estate, Utilities.
maxPriceNoMaximum price in USD (forex: the quoted rate).
minPriceNoMinimum price in USD (forex: the quoted rate).
directionNodesc for largest first, asc for smallest first.desc
maxChangeNoMaximum 24h change in percent; -5 finds assets down 5% or more.
minChangeNoMinimum 24h change in percent; 5 means +5%, -3 means -3%.
minVolumeNoMinimum 24h volume as reported: shares for stocks and ETFs, USD for crypto.
minMarketCapNoMinimum market cap in USD; 1000000000000 is $1T. Any value above 0 excludes assets with no market cap, such as forex and many ETFs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / direction / description
      Added value: +"desc for largest first, asc for smallest first."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum assets to return."
    • addedInput schema / properties / maxChange / description
      Added value: +"Maximum 24h change in percent; -5 finds assets down 5% or more."
    • addedInput schema / properties / maxPrice / description
      Added value: +"Maximum price in USD (forex: the quoted rate)."
    • addedInput schema / properties / minChange / description
      Added value: +"Minimum 24h change in percent; 5 means +5%, -3 means -3%."
    • addedInput schema / properties / minMarketCap / description
      Added value: +"Minimum market cap in USD; 1000000000000 is $1T. Any value above 0 excludes assets with no market cap, such as forex and many ETFs."
    • addedInput schema / properties / minPrice / description
      Added value: +"Minimum price in USD (forex: the quoted rate)."
    • addedInput schema / properties / minVolume / description
      Added value: +"Minimum 24h volume as reported: shares for stocks and ETFs, USD for crypto."
    • addedInput schema / properties / sector / description
      Added value: +"Stocks and ETFs only; exact name, case-insensitive: Technology, Healthcare, Financial Services, Consumer Cyclical, Consumer Defensive, Communication Services, Industrials, Energy, Basic Materials, Real Estate, Utilities."
    • addedInput schema / properties / sort / description
      Added value: +"Field to rank by. Use change24h with direction desc for top gainers, asc for top losers."
    • addedInput schema / properties / type / description
      Added value: +"Only this asset class."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description adds genuinely new context beyond them: data comes from a snapshot refreshing roughly every 15 minutes (freshness caveat) and results are capped at 25 assets, which matters for result interpretation.

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

Conciseness5/5

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

Three sentences, front-loaded with the capability, then examples, then constraints and the hand-off to get_fundamentals. No filler and no repetition of schema enums.

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

Completeness4/5

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

For an 11-parameter screening tool with no output schema, the description covers scope, freshness, result cap, filter semantics, and out-of-scope cases. Minor gap: it doesn't hint at what fields come back per asset (price, change, volume, market cap), leaving the agent to infer the return shape.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds cross-parameter semantics the schema cannot express — that all filters are AND-combined and independently optional — plus the universe note that market-cap filters exclude forex and many ETFs, which helps the agent reason across parameters.

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 (find) and resource (assets) plus the exact filter dimensions, sortability, and universe scope (stocks, ETFs, crypto, commodities, forex). The three example queries make the tool's role unmistakable versus siblings like get_fundamentals or get_asset_quote.

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 concrete use cases ("biggest movers today", "tech stocks over $1T", "cheapest crypto"), states all filters are optional and AND-combined, and explicitly excludes valuation screens like P/E by routing to get_fundamentals. Both when-to-use and when-not-to-use are covered with a named alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mkts Market Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources