Skip to main content
Glama

Sector market cap and volume over time

get_market
Read-only

Returns the tracked companies as one market over time: combined market cap, each segment's or company's weight, and traded dollar volume. Daily up to a year, weekly over five years; or, with view: 'map', one session company by company. A past day's market cap is that day's close times the shares outstanding then (SEC filings); the last point is the latest session whose official closes are in, so during a session it is the previous one. notes explains units and gaps. Use it for how the sector, a segment or a company's weight has changed; for today, get_market_overview.

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

Input Schema

NameRequiredDescriptionDefault
dateNoMap: a session date (YYYY-MM-DD) among the last 40; default the latest. A day without a session gives the latest session before it (`requestedDate` says so); a date before the sessions kept is refused.
viewNo'series' (default): totals and their breakdown over time. 'map': one session, company by company.
rangeNoSeries: 1m, 3m, 6m, 1y (default) or 5y (weekly points).
pointsNoSeries: keep at most this many points, evenly spaced from the end (default 60, max 400).
sectorNoSeries: 'all' (default) breaks the universe down by segment; a segment id, compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other: breaks that segment down by company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sector / description
      Previous value: -"Series: 'all' (default) breaks the universe down by segment; a segment id — compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other — breaks that segment down by company."New value: +"Series: 'all' (default) breaks the universe down by segment; a segment id, compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other: breaks that segment down by company."
  2. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Map: a session date (YYYY-MM-DD) among the last 40; default the latest. A day without a session gives the latest session before it (`requestedDate` says so)."New value: +"Map: a session date (YYYY-MM-DD) among the last 40; default the latest. A day without a session gives the latest session before it (`requestedDate` says so); a date before the sessions kept is refused."
  3. Changed5 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"Map: a session date (YYYY-MM-DD) among the last 40; default the latest."New value: +"Map: a session date (YYYY-MM-DD) among the last 40; default the latest. A day without a session gives the latest session before it (`requestedDate` says so)."
    • addedInput schema / properties / range / enum
      Added value: +[
      +  "1m",
      +  "3m",
      +  "6m",
      +  "1y",
      +  "5y"
      +]
    • changedInput schema / properties / sector / description
      Previous value: -"Series: 'all' (default) breaks the universe down by segment; a segment id — compute, platform, software, power, memory, equipment, interconnect, systems, neocloud, optics, other — breaks that segment down by company."New value: +"Series: 'all' (default) breaks the universe down by segment; a segment id — compute, interconnect, optics, memory, systems, power, neocloud, equipment, software, platform, other — breaks that segment down by company."
    • addedInput schema / properties / sector / enum
      Added value: +[
      +  "all",
      +  "compute",
      +  "interconnect",
      +  "optics",
      +  "memory",
      +  "systems",
      +  "power",
      +  "neocloud",
      +  "equipment",
      +  "software",
      +  "platform",
      +  "other"
      +]
    • addedInput schema / properties / view / enum
      Added value: +[
      +  "series",
      +  "map"
      +]
  4. Changed2 schema fields changed
    • addedInput schema / properties / points / maximum
      Added value: +400
    • addedInput schema / properties / points / minimum
      Added value: +5
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, non-destructive tool. The description adds substantive behavior beyond them: daily vs weekly granularity, map-mode scope, the SEC-filing basis for historical market cap, the last-point timing caveat during a session, and the presence of notes explaining units and gaps.

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 front-loaded with what the tool returns and is organized around output, granularity, caveats, and usage. Despite covering several behavioral details, every sentence contributes useful context and none is redundant.

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?

For a five-parameter read-only tool with no output schema, the description is complete enough to call correctly. It explains the returned fields, temporal granularity, map-mode behavior, historical calculation caveat, and where units/gaps are documented.

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?

Schema description coverage is 100%, so the schema already documents each parameter in detail. The description still adds useful cross-parameter meaning by explaining how view: 'map' changes the result to one session company by company and by clarifying daily vs weekly range behavior, though it does not elaborate on points or sector beyond the schema.

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 states specific outputs: combined market cap, segment/company weights, and traded dollar volume over time. It also explicitly distinguishes itself from the sibling tool get_market_overview for today's data, so an agent can identify its role without opening the 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?

It gives explicit when-to-use guidance: use this to see how the sector, a segment, or a company's weight has changed, and use get_market_overview for today. The daily/weekly and series/map modes are also described, making the intended invocation context clear.

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.