Skip to main content
Glama
Sign In
cse-mcp

cse-mcp

by lxnid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Market overview

get_market_overview
Read-onlyIdempotent

Retrieve a real-time market snapshot—open/closed status, ASPI and S&P SL20 values, changes, ranges, today's turnover, volume, and trades—to quickly see how the market is doing.

Instructions

Snapshot of the whole market right now: open/closed status, the ASPI and S&P SL20 indices (value, change, day range) and today's turnover, volume and trades. Best first call for "how is the market doing?".

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": "get_market_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description's remaining burden is scope and freshness. It adds real value there by pinning the tool to a current-moment snapshot and enumerating the data surfaces included, which tells the agent the data is live rather than historical. It does not discuss staleness, refresh cadence or market-closed behavior, so it is not fully transparent.

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?

Two short sentences, both earning their place: the first front-loads the data contents, the second front-loads the selection cue. There is no boilerplate, hedging or repetition.

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?

With zero parameters, rich annotations and an output schema handling return values, the description only needs to cover purpose, contents and selection. It does all three, so an agent can call it correctly with no additional inference.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly signals that no scoping inputs (symbol, date, exchange) are accepted, since it is a whole-market snapshot.

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 resource (whole-market snapshot) with an explicit inventory of what it returns: open/closed status, ASPI and S&P SL20 values with change and day range, plus turnover, volume and trades. The 'right now'/'today's' framing distinguishes it from history and daily-summary siblings without needing to name them.

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?

Gives an explicit routing rule — 'Best first call for "how is the market doing?"' — which maps a user intent directly to this tool. It stops short of naming when NOT to use it or pointing at specific alternatives such as the daily summary or index history, so it is clear but not exhaustive.

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