Skip to main content
Glama

Market map

market_map
Read-onlyIdempotent

The US stock market on StockMap's map: the 11 sectors, each with its share of the market, its 2-week lean from the model's nightly calls on its stocks, its move on the day and its best and worst stock. A summary, not every stock. Use it when someone asks how the US market looks, or which sectors lead or lag. Its card draws the market as StockMap's heatmap of every sector's biggest stocks, or as bubbles, live in market hours. Each answer carries the not-advice line and the run date.

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_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoHow the card draws the market: "map", StockMap's heatmap of every sector's biggest stocks, or "bubbles", the biggest stocks as bubbles sized by market valuemap
scopeNoWhich stocks the card draws: "all", every US stock StockMap maps, or "sp500", the S&P 500'sall

Output Schema

NameRequiredDescriptionDefault
runYes
viewNoHow the card draws the market: the heatmap or the bubblesmap
scopeNoWhich stocks the card draws: every US stock, or the S&P 500'sall
stocksYesThe stocks on the map
map_urlNohttps://stockmap.io/heatmap
sectorsYesBiggest first
not_adviceNoThe model's track-recorded read, not financial advice.
sectors_urlNohttps://stockmap.io/sectors

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / scope
      Added value: +{
      +  "default": "all",
      +  "description": "Which stocks the card draws: \"all\", every US stock StockMap maps, or \"sp500\", the S&P 500's",
      +  "enum": [
      +    "all",
      +    "sp500"
      +  ],
      +  "title": "Scope",
      +  "type": "string"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "default": "map",
      +  "description": "How the card draws the market: \"map\", StockMap's heatmap of every sector's biggest stocks, or \"bubbles\", the biggest stocks as bubbles sized by market value",
      +  "enum": [
      +    "map",
      +    "bubbles"
      +  ],
      +  "title": "View",
      +  "type": "string"
      +}
    • addedOutput schema / properties / scope
      Added value: +{
      +  "default": "all",
      +  "description": "Which stocks the card draws: every US stock, or the S&P 500's",
      +  "enum": [
      +    "all",
      +    "sp500"
      +  ],
      +  "title": "Scope",
      +  "type": "string"
      +}
    • addedOutput schema / properties / view
      Added value: +{
      +  "default": "map",
      +  "description": "How the card draws the market: the heatmap or the bubbles",
      +  "enum": [
      +    "map",
      +    "bubbles"
      +  ],
      +  "title": "View",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description adds genuinely new context: the card renders live during market hours, and every answer carries a not-advice line and the run date. It does not discuss caching or latency limits, but for a read-only snapshot tool this is solid extra disclosure.

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?

The content is front-loaded with the resource and its scope, then usage, then presentation behavior — a sensible order with no filler sentences. The middle sentences are densely packed and partially duplicate the enum descriptions, costing a little tightness.

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?

An output schema exists, so return structure needn't be spelled out, and the description still covers data currency (run date, live market hours) and the not-advice disclaimer. Combined with the fully documented two-parameter schema, an agent has enough to call this correctly.

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% and both parameters are enums with full descriptions, so the schema does the heavy lifting. The description restates the same two rendering options (heatmap vs. bubbles) without adding syntax or interaction detail beyond what the schema already provides.

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?

The description names a concrete resource and enumerates exactly what it returns: the 11 US sectors with market share, 2-week model lean, daily move, and best/worst stock. It is readily distinguishable in content from siblings like sector or compare_stocks, though it never names those siblings explicitly.

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?

"Use it when someone asks how the US market looks, or which sectors lead or lag" gives a clear triggering condition, and "A summary, not every stock" sets a scope boundary. It stops short of naming the alternative tool (e.g., sector for a single-sector drill-down), so routing is implied rather than explicit.

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