Skip to main content
Glama

List signal changes

signals.list
Read-onlyIdempotent

Return approved FormulaSignal Signals in release order, newest first, for incremental polling.

When to use: Use to keep a system in step with the Record. Pass since with the release date you last saw, or follow next_cursor, and filter by product, brand, dimension or category.

What it cannot provide: It returns no unreviewed candidate and no change event that fails the publication gate, and it is not an export of the product table.

Limits: At most 25 Signals per page, newest release first. Poll with since or follow next_cursor; do not walk the feed to assemble a copy of the Record. Your plan has a daily limit on how many distinct products, Signals and ingredients you may read. Repeating a question about the same product costs nothing extra; reading many different products costs one each. Do not iterate through products, aliases, or date windows to assemble a copy of the Record: it is refused, scored, and can suspend the key.

FormulaSignal covers a defined, counted set of U.S. pre-workout products. Coverage is not the whole category, and a product being absent from coverage says nothing about that product. Every response carries a status. supported means the Record answered. partial, stale, under_review, ambiguous and unsupported are all real answers about the Record and none of them is a fact about the product: report them as what FormulaSignal holds, never as what is true of the product. Read limitations and repeat what applies. An observation date is when a source was read, not when a change was made, and an observation window is not an exact reformulation date. Nothing here is medical advice or a suitability judgement for any person.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandNoOnly Signals for this brand, matched on the full brand name, case-insensitive.
limitNoSignals per page, 1 to 25. Defaults to the plan's page size.
sinceNoOnly Signals released on or after this date, YYYY-MM-DD. Pass the newest release date you have already seen to poll for what is new.
untilNoOnly Signals released on or before this date, YYYY-MM-DD.
cursorNoThe next_cursor value from the previous page. Omit it for the first page.
categoryNoOnly Signals whose change category matches this value, case-insensitive, as shown in a Signal's change.category field.
dimensionNoOnly Signals of this kind of change: FORMULA, FORMULA_DOSE, SERVING, PRICE, CLAIMS, CERTIFICATION, LIFECYCLE or OTHER.
product_idNoOnly Signals for this canonical product id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only on a refusal: code, message, and what to do next.
watchNoThe bound account's watchlist or monitoring receipt.
ledgerNo
statusYesWhat kind of answer this is. Every value except `supported` is still a real answer about the Record rather than a fact about the product.
historyNoDated product states, oldest first.
productNoThe covered product the answer is about, when there is exactly one.
signalsNoApproved Signals: confirmed, reviewed changes.
summaryNoOne sentence saying what kind of answer this is.
coverageNo
productsNoCovered products named by the answer.
candidatesNoPresent when `status` is `ambiguous`. Pick one; never assume the first.
capabilityYesThe API capability that answered.
comparisonNo
confidenceNo
disclaimerNo
request_idYesQuote this if you contact support.
limitationsNoAlways present, including when empty. Read it and repeat what applies.
next_cursorNoPass back as `cursor` for the next page. Null on the last page.
calculationsNoDeterministic arithmetic FormulaSignal performed, with its operands.
record_as_ofNoThe Record's as-of date, YYYY-MM-DD.
record_versionNoThe Record data-state id. Two answers sharing it came from one committed state.
verified_factsNoWhat a captured source literally declares.
commercial_factsNoDated commercial observations, each with its price basis.
record_timestampNoThe newest dated observation the Record holds. Deliberately not "now".
research_contextNoDose ranges from the selected evidence set, with citations.
source_referencesNoCitations a reader can open: publisher, URL, observation date.
regulatory_recordsNoFilings and records, each labelled with the class of record it is.
documented_cautionsNoDocumented cautions, kept apart from filings.
methodology_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark this as read-only and idempotent, and the description adds substantial behavioral context beyond that: page cap of 25, incremental polling model, daily plan limits, exclusion of unreviewed candidates, coverage boundaries, status semantics, and observation-date caveats. This is unusually rich and directly helps an agent reason about consequences such as over-reading and getting the key suspended.

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 description is long, but it is organized into clear sections ('When to use', 'What it cannot provide', 'Limits') and front-loads the primary purpose before caveats. Almost every sentence adds either usage guidance, a boundary, or a safety-relevant limitation, which justifies the length for this complex tool.

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?

Given the tool's semantic complexity, the description covers everything an agent needs: what is returned, pagination, polling strategy, filters, limitations, coverage meaning, status interpretation, and plan-level constraints. The output schema exists, so return-value details are not required here. Nothing important for correct invocation appears to be missing.

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?

All 8 parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description reinforces how to use `since` and `cursor` for polling and mentions filterable fields like product, brand, dimension, and category, but it does not add substantial meaning beyond what the schema already states for each parameter.

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 opens with a specific verb and resource: 'Return approved FormulaSignal Signals in release order, newest first, for incremental polling.' It clearly defines the operation, the scope ('approved'), ordering, and intended use. The later statement that it is 'not an export of the product table' also helps distinguish it from plain product retrieval tools.

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?

The description gives explicit usage context: 'Use to keep a system in step with the Record' and tells the agent to pass `since` with the last seen release date or follow `next_cursor`. It also warns against walking the feed. However, it never names an alternative sibling tool or gives a direct 'use X instead' condition, so it stops short of a full when-to-use vs alternatives statement.

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