Skip to main content
Glama

Market overview

market_overview
Read-only

ONE SNAPSHOT OF BOTH MARKETS, no arguments. Top instruments across crypto AND US stocks together, ranked by Martingale Score (0-5), with their Startingale readings: a general picture of both markets at once. crypto_overview and stock_overview cover a single asset class; search_instruments takes a count and filters. Answers in formatted text. Costs 10 units of the monthly quota, the highest cost of the seven tools, since it reads both catalogues; the single-class overviews cost half.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real context beyond that: no arguments required, formatted-text response, and a quota cost that is the highest of the seven tools because it reads both catalogues. It does not say how many instruments are returned or how ties/zero-score items are handled, and the term "Startingale readings" is unexplained.

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

Conciseness4/5

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

Front-loaded with the core action in capitals, followed by scope, alternatives, and cost. Slightly dense and the closing cost sentence is long, but no sentence is purely filler.

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 a zero-parameter, read-only aggregate tool with no output schema, the definition covers scope, output format ('formatted text'), safety via annotations, and cost. The one meaningful gap is how many instruments the snapshot contains, which affects interpretation of results.

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 and the description correctly states 'no arguments', which is the appropriate baseline for an argument-free tool. Nothing further is needed on parameter meaning.

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 and scope: a single snapshot of top instruments across crypto AND US stocks, ranked by Martingale Score (0-5). It explicitly contrasts itself with crypto_overview/stock_overview (single asset class) and search_instruments (count + filters), so an agent can discriminate it without opening a schema.

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 clear selection criteria: use it for a combined picture of both markets, use the single-class overviews for one asset class, use search_instruments when a count or filters are needed. The cost disclosure (10 units vs half for single-class) adds an explicit trade-off for routing decisions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources