Skip to main content
Glama

Stored series

series

Manage stored macroeconomic and driver data: search, retrieve as-of values, add sources, and fetch updates for Bayesian VAR stress tests.

Instructions

Stored series. Actions: search, get, add, update.

update fetches the named ids; with quantity it instead discovers the objects of that driver quantity and fetches their series.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "series"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe series id that get reads: a macro variable like ru.key_rate, or a driver like share_price:sibn.
idsNoThe series ids update fetches; every known series when omitted. FRED needs the FRED_API_KEY environment variable.
textNoThe words search looks for, in the ids and loaders of the known sources.
as_ofNoThe date get works as of, YYYY-MM-DD: only values published by then are returned. Today when omitted.
entryNoThe source entry add writes to the workspace sources.toml: the table of one source plus its id.
actionYesWhat to do: search for series, get one as known on a date, add a source, or update (fetch) as a job.
quantityNoA driver quantity, e.g. share_price: update discovers its objects and fetches their series instead of ids.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.0.2
    • addedInput schema / properties / action / description
      Added value: +"What to do: search for series, get one as known on a date, add a source, or update (fetch) as a job."
    • addedInput schema / properties / as_of / description
      Added value: +"The date get works as of, YYYY-MM-DD: only values published by then are returned. Today when omitted."
    • addedInput schema / properties / entry / description
      Added value: +"The source entry add writes to the workspace sources.toml: the table of one source plus its id."
    • addedInput schema / properties / id / description
      Added value: +"The series id that get reads: a macro variable like ru.key_rate, or a driver like share_price:sibn."
    • addedInput schema / properties / ids / description
      Added value: +"The series ids update fetches; every known series when omitted. FRED needs the FRED_API_KEY environment variable."
    • addedInput schema / properties / quantity / description
      Added value: +"A driver quantity, e.g. share_price: update discovers its objects and fetches their series instead of ids."
    • addedInput schema / properties / text / description
      Added value: +"The words search looks for, in the ids and loaders of the known sources."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare non-read-only, open-world, non-idempotent behavior. The description adds useful detail about update fetching named ids or discovering series via a driver quantity, but it does not disclose the mutating nature of add or the practical behavior of search and get.

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 text is short and front-loads the action list. It spends disproportionate space on update while leaving other actions unexplained, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-action tool with seven parameters and mutation, the description is thin. The rich schema descriptions and output schema compensate substantially, but the description still lacks per-action usage guidance.

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 each parameter is already tied to its action in the schema. The description reinforces only the update quantity behavior, adding little beyond the structured parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Stored series') and enumerates four actions, which gives some sense of scope. However, it does not define what those actions do beyond the update nuance, and 'Stored series' largely restates the title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It lists search, get, add, and update but does not say when to use each action or how to choose between them. The only routing guidance is the ids-versus-quantity distinction for update.

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