Skip to main content
Glama
TickerDB

TickerDB

Official

get_market

Read-only

Retrieve point-in-time US equity market and macroeconomic regime rows by date, with optional change-only filtering to identify dates when market or macro bands shifted.

Instructions

Market-level rows, one per date, point in time: US equity market regime (market_*) and economy (macro_*) bands and values, e.g. market_regime_zone, macro_yield_curve_zone. changes=true returns only dates where a band changed. Field list: get_schema level=market. To find tickers under a regime, put market_/macro_ filters into query.

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
endNoRange end (YYYY-MM-DD).
dateNoOne date (YYYY-MM-DD).
limitNoRange rows; default 100.
orderNoDefault desc.
startNoRange start (YYYY-MM-DD).
appendNoAdd rows to an existing store_as table instead of replacing it.
fieldsNoJSON array of market fields; ["*"] adds change markers.
changesNotrue: only dates where any band changed. Or a JSON array of the bands to watch.
filtersNoJSON array of {field, op, value} on market fields.
store_asNoTable name: store rows in SQLite, return only a summary. Read with query_data.
fetch_allNoFollow every page into store_as in this one call.
timeframeNoDefault daily.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool's result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only and non-destructive profile, and the description adds genuinely new semantics: one row per date, point-in-time values, and that changes=true narrows output to dates where a band changed. It also notes ['*'] in fields adds change markers, which is behavior not visible from annotations.

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 definition is short and front-loads what the tool returns before the opt-in behaviors and cross-references. It is telegraphic enough that a few clauses ('Field list: get_schema level=market') read as fragments, but every sentence carries usable information.

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 12 optional parameters and an output schema present, the description need not explain return shapes; it still covers the key non-obvious behaviors (per-date rows, changes filtering, field discovery, ticker-lookup alternative). Pagination and store_as/fetch_all behavior are left entirely to the schema, which is acceptable given an output schema exists.

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 coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema for changes (global change filter, not just the schema's array form) and for the ['*'] marker in fields. The interaction between filters and market_/macro_ fields and the pointer to query for ticker-level filtering is also added context.

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 states the resource precisely: market-level rows, one per date, point-in-time, covering market_* and macro_* bands. It distinguishes itself from query by redirecting ticker-level lookups there, though the verb is implicit (the read is implied rather than stated).

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?

It gives a concrete routing rule: 'To find tickers under a regime, put market_/macro_ filters into query,' which is an explicit alternative and the condition that selects it. It also points to get_schema level=market for field discovery, but does not state when not to use get_market (e.g. single-date vs range vs stored-table reading).

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