FormulaSignal

Get category snapshot

signals.snapshot

Read-onlyIdempotent

Return a bounded summary of approved Signals and coverage state across the covered pre-workout set for a date window.

When to use: Use for 'what changed in the category recently'. Pass from and to dates; the window is capped and the page size is capped.

What it cannot provide: It is not an export. It returns approved Signals inside one bounded window, never the product table and never the underlying Record.

Limits: Bounded window of at most 400 days and at most 25 items per page. Follow next_cursor for more. 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

Name	Required	Description
`to`	No	End of the window, YYYY-MM-DD. Defaults to today (UTC).
`from`	No	Start of the window, YYYY-MM-DD. Defaults to the widest window the plan allows before `to`.
`limit`	No	Signals per page, 1 to 25. Defaults to the plan's page size.
`cursor`	No	The next_cursor value from the previous page. Omit it for the first page.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only on a refusal: code, message, and what to do next.
`watch`	No	The bound account's watchlist or monitoring receipt.
`ledger`	No
`status`	Yes	What kind of answer this is. Every value except `supported` is still a real answer about the Record rather than a fact about the product.
`history`	No	Dated product states, oldest first.
`product`	No	The covered product the answer is about, when there is exactly one.
`signals`	No	Approved Signals: confirmed, reviewed changes.
`summary`	No	One sentence saying what kind of answer this is.
`coverage`	No
`products`	No	Covered products named by the answer.
`candidates`	No	Present when `status` is `ambiguous`. Pick one; never assume the first.
`capability`	Yes	The API capability that answered.
`comparison`	No
`confidence`	No
`disclaimer`	No
`request_id`	Yes	Quote this if you contact support.
`limitations`	No	Always present, including when empty. Read it and repeat what applies.
`next_cursor`	No	Pass back as `cursor` for the next page. Null on the last page.
`calculations`	No	Deterministic arithmetic FormulaSignal performed, with its operands.
`record_as_of`	No	The Record's as-of date, YYYY-MM-DD.
`record_version`	No	The Record data-state id. Two answers sharing it came from one committed state.
`verified_facts`	No	What a captured source literally declares.
`commercial_facts`	No	Dated commercial observations, each with its price basis.
`record_timestamp`	No	The newest dated observation the Record holds. Deliberately not "now".
`research_context`	No	Dose ranges from the selected evidence set, with citations.
`source_references`	No	Citations a reader can open: publisher, URL, observation date.
`regulatory_records`	No	Filings and records, each labelled with the class of record it is.
`documented_cautions`	No	Documented cautions, kept apart from filings.
`methodology_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 27, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds substantial context: the capped window (400 days, 25 per page), the daily read limits, and the nuanced meaning of status values like 'partial' and 'stale', emphasizing they are not facts about the product. This exceeds what annotations provide, though it does not cover every potential behavior (e.g., pagination mechanics are implied via next_cursor).

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 efficient, front-loading the core purpose and then covering usage, limits, and interpretation. Every sentence earns its place, though the section on statuses and disclaimers is a bit dense. It could be trimmed, but it is not verbose. Slightly above average in structure.

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 complexity (bounded windows, status semantics, daily limits) and the presence of an output schema (which handles return structure), the description is complete enough. It clarifies the tricky aspects (coverage is not the whole category, observation dates vs. reformulation) that an agent needs to interpret results correctly. No critical gaps remain.

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 description coverage is 100%, meaning the schema already documents each parameter clearly (dates, limit, cursor). The description adds context on defaults and caps, but these are also implied by schema descriptions. The description does not add novel meaning beyond what the schema provides, so a baseline 3 is appropriate.

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 a specific verb ('Return a bounded summary') and resource ('approved Signals and coverage state across the covered pre-workout set for a date window'), making it distinct from siblings like signals.list and ledger.get. It clearly identifies what it provides and what it is not (not an export), which separates it from alternatives.

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?

The description explicitly states when to use it ('Use for 'what changed in the category recently'') and what it cannot provide (not an export), and it names alternatives implicitly through sibling context. It also warns against misuse (e.g., iterating to assemble a copy of the Record), which is strong usage guidance.

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

All FormulaSignal tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?