Skip to main content
Glama
Sign In
cse-mcp

cse-mcp

by lxnid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search and rank stocks

list_stocks
Read-onlyIdempotent

Search listed stocks by company name or ticker, then rank results by turnover, price change, market cap, volume, or symbol using today's prices; set limit to 0 to return all matches.

Instructions

Search and rank every listed stock with today's prices.

Use `query` to find symbols by company name or ticker (e.g. "bank", "hayleys", "JKH").
Sort by turnover, change_pct (best first), market_cap, volume or symbol.
Set limit=0 to return every match.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
sort_byNoturnover

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds real value beyond that: it discloses that prices are today's, that results are ranked, and that limit=0 returns every match — a useful warning about a potentially unbounded result set. It does not mention pagination or rate limits, keeping it short of 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?

Three short lines, front-loaded with purpose and followed by per-parameter guidance. Every sentence carries information and there is no filler or redundancy.

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?

With an output schema present, return shape need not be described, and the annotations plus the parameter guidance cover the rest of what an agent needs. Minor residual ambiguity remains around market/currency context (the examples suggest a single exchange) and behavior when the market is closed, but nothing essential to invoking the tool is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the whole burden, and it does: query is explained as company-name or ticker matching with concrete examples ("bank", "hayleys", "JKH"), sort_by's accepted values are enumerated, and limit=0 is defined as return-all. All three parameters gain meaning not present in the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Search and rank every listed stock with today's prices" gives a concrete verb pair (search, rank) and a clear resource scope (all listed stocks), which implicitly separates it from get_stock (single symbol) and get_top_movers. It stops short of naming a sibling or stating the exclusion explicitly, so it lands just below the top of the scale.

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

Usage Guidelines3/5

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

The description supplies operational guidance for each parameter (use query for name/ticker lookup, sortable fields, limit=0 for all matches) but gives no when-to-use / when-not-to-use framing against siblings such as get_stock or get_top_movers. Usage is implied by the parameter hints rather than stated as a routing rule.

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

Deploy Server

Other Tools