Skip to main content
Glama

CeylonCharts - Colombo Stocks Exchange (CSE) data for AI Agents

by com.ceyloncharts.mcp
OverviewDiscussionsAdmin

Screen stocks

screen_stocks
Read-onlyIdempotent

Screen CSE stocks by pre-computed technical criteria (moving-average position, relative-strength rating, 52-week range, unusual volume). Every filter is optional and AND-combined; omit a filter to not constrain on it. E.g. above_ema50=true & above_ema200=true & rs_rating_min=80 finds market-leading uptrends; is_52w_high=true finds stocks making new highs today; vol_vs_sma50_pct_min=100 finds unusual volume (trading at 2x+ its 50-day average). Returns CSV, one row per matching stock.

Input Schema

NameRequiredDescriptionDefault
dateNoTrading date to evaluate the screen as of, in YYYY-MM-DD format. Defaults to the latest available trading date when omitted.
sortNoColumn to rank results by. Defaults to rs_rating (relative-strength rating) when omitted.
limitNoMax results to return; the underlying screener defaults to 20 when omitted.
orderNoSort direction. Default desc.
is_hv1NoFilter to stocks with the highest volume in the past 252 trading days.
is_hveNoFilter to stocks with the highest volume ever recorded today.
sectorNoOptional substring filter against the company sector name, e.g. "bank" or "materials".
is_hvytdNoFilter to stocks with the highest volume year-to-date.
is_52w_lowNoFilter to stocks at a 52-week low today.
above_ema21NoWhen set, filters to results whose price is currently above (true) or below (false) its 21-day exponential moving average.
above_ema50NoWhen set, filters to results whose price is currently above (true) or below (false) its 50-day exponential moving average.
above_sma10NoWhen set, filters to results whose price is currently above (true) or below (false) its 10-day simple moving average.
is_52w_highNoFilter to stocks at a 52-week high today.
above_ema200NoWhen set, filters to results whose price is currently above (true) or below (false) its 200-day exponential moving average — a long-term trend filter.
rs_rating_maxNoMaximum relative-strength rating (1-99 percentile rank vs. the whole market) to include.
rs_rating_minNoMinimum relative-strength rating (1-99 percentile rank vs. the whole market). E.g. 80+ for market leaders.
change_pct_maxNoOnly include results whose today's percentage price change is at most this value (e.g. -5 for a -5% or worse move).
change_pct_minNoOnly include results whose today's percentage price change is at least this value (e.g. 5 for a +5% or greater move).
vol_vs_sma50_pct_maxNoMaximum volume-vs-50-day-average percent.
vol_vs_sma50_pct_minNoMinimum today's volume vs. its 50-day average volume, as a percent (e.g. 100 = 2x average).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / above_ema200 / description
      Previous value: -"Filter by price above/below its 200-day exponential moving average (long-term trend filter)."New value: +"When set, filters to results whose price is currently above (true) or below (false) its 200-day exponential moving average — a long-term trend filter."
    • changedInput schema / properties / above_ema21 / description
      Previous value: -"Filter by price above/below its 21-day exponential moving average."New value: +"When set, filters to results whose price is currently above (true) or below (false) its 21-day exponential moving average."
    • changedInput schema / properties / above_ema50 / description
      Previous value: -"Filter by price above/below its 50-day exponential moving average."New value: +"When set, filters to results whose price is currently above (true) or below (false) its 50-day exponential moving average."
    • changedInput schema / properties / above_sma10 / description
      Previous value: -"Filter by price above/below its 10-day simple moving average."New value: +"When set, filters to results whose price is currently above (true) or below (false) its 10-day simple moving average."
    • changedInput schema / properties / change_pct_max / description
      Previous value: -"Maximum today's percent change."New value: +"Only include results whose today's percentage price change is at most this value (e.g. -5 for a -5% or worse move)."
    • changedInput schema / properties / change_pct_min / description
      Previous value: -"Minimum today's percent change."New value: +"Only include results whose today's percentage price change is at least this value (e.g. 5 for a +5% or greater move)."
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD. Defaults to the latest available trading date."New value: +"Trading date to evaluate the screen as of, in YYYY-MM-DD format. Defaults to the latest available trading date when omitted."
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 20, max 100)."New value: +"Max results to return; the underlying screener defaults to 20 when omitted."
    • changedInput schema / properties / rs_rating_max / description
      Previous value: -"Maximum relative-strength rating (1-99)."New value: +"Maximum relative-strength rating (1-99 percentile rank vs. the whole market) to include."
    • changedInput schema / properties / sort / description
      Previous value: -"Column to sort by. Default rs_rating."New value: +"Column to rank results by. Defaults to rs_rating (relative-strength rating) when omitted."
  2. First observed

TDQS

A4.5/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 safety is covered; the description adds the return contract ('Returns CSV, one row per matching stock') and the optional-AND-filter semantics, which the annotations do not convey. It omits any note on rate limits, result caps, or screening-date behavior, keeping it from a 5.

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?

Four sentences, front-loaded with purpose, then combinatorics, then compact worked examples, then the return format. No filler and every sentence carries distinct information.

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 20-parameter screening tool with no output schema, the description covers purpose, filter semantics, examples, and the CSV return shape, while the schema fully documents each parameter and its defaults. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so baseline is 3, but the description adds value beyond the schema: it explains filter-combination semantics (optional, AND-combined) and gives concrete examples with expected interpretations (above_ema50 & above_ema200 & rs_rating_min=80 = market-leading uptrends; vol_vs_sma50_pct_min=100 = 2x average volume).

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+resource+domain ('Screen CSE stocks by pre-computed technical criteria') and enumerates the criterion families (MA position, RS rating, 52-week range, unusual volume). This clearly distinguishes it from siblings like get_technicals (single-symbol) and screen_indices (indices rather than stocks).

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

Usage Guidelines4/5

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

Explicitly explains the combinatorics ('every filter is optional and AND-combined; omit a filter to not constrain on it') and gives three worked filter combinations showing intended usage. It does not name a sibling alternative or state when NOT to use this tool (e.g., versus get_technicals for a single symbol), so it stops short of a 5.

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

All CeylonCharts - Colombo Stocks Exchange (CSE) data for AI Agents 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