Skip to main content
Glama
sahmk-sa

sahmk-mcp

by sahmk-sa

get_market_movers

Retrieve top gainers, losers, volume leaders, or value leaders for Saudi market indices (TASI, NOMU). Specify mover type and optional count.

Instructions

Get market movers in one curated endpoint. Use this for top gainers, top losers, highest volume leaders, or highest value leaders. Returns a stable schema: type, index, count, items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesMover type: 'gainers', 'losers', 'volume', or 'value'.
limitNoOptional number of results from 1 to 50.
indexNoOptional market index: 'TASI' or 'NOMU' (alias 'NOMUC' is accepted and normalized).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It notes the output schema is stable and lists fields, but does not mention read-only nature, authentication needs, or rate limits. Adequate but not exhaustive.

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?

The description is extremely concise: two sentences. The first sentence states the tool's purpose, the second provides usage guidance and output schema. No wasted words.

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?

Given the presence of an output schema and 100% parameter coverage, the description is largely complete. It could optionally mention the default limit or index behavior, but the core information is present.

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%, so baseline is 3. The description adds no parameter information beyond what the schema already provides (e.g., types, index values). No extra semantics.

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 clearly states the tool retrieves market movers, a specific resource, and lists explicit use cases (top gainers, losers, volume, value leaders). It distinguishes itself from sibling tools which focus on individual symbols, sectors, or quotes.

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?

The description explicitly says 'Use this for top gainers, top losers, highest volume leaders, or highest value leaders,' providing clear guidance on when to employ this tool versus siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sahmk-sa/sahmk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server