Skip to main content
Glama

Watch product

watchlist.add
Idempotent

Add one covered product to the bound account's watchlist.

When to use: Use when a person asks to start watching a product. Resolve the product first if you were given a name rather than an id.

What it cannot provide: It cannot add a product outside the covered set, exceed the account's watch limit, or act on an account this key is not bound to. It refuses a covered product FormulaSignal cannot monitor yet and says why in the refusal. It does not start a subscription and refuses when the account is not entitled.

Limits: 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
product_idYesThe canonical product id to start watching. Resolve a name with products.resolve first.

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.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses refusal conditions (outside covered set, watch limit, account binding, entitlement), anti-scraping enforcement ('can suspend the key'), and the meaning of statuses. It also explains that absence from coverage says nothing about the product, which is valuable behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with labeled sections and front-loads the purpose, but it is lengthy and includes generic FormulaSignal caveats (statuses, observation dates, medical advice) that are not specific to adding to a watchlist. Some sentences could be trimmed without losing essential guidance.

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 output schema exists, the description covers all necessary operational context: prerequisites, coverage constraints, account binding, watch limits, refusal behavior, plan limits, and response status semantics. An agent has enough information to call the tool correctly and avoid misuse.

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?

The single parameter is already fully described in the schema (canonical product id, resolve names first), so the description adds little new parameter-specific meaning. It reinforces the need to resolve names, but schema coverage is 100%, so baseline 3 applies.

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: 'Add one covered product to the bound account's watchlist.' This clearly identifies the operation and scope, and the 'Watch product' title aligns with the add-to-watchlist action, distinguishing it from sibling tools like watchlist.remove and watchlist.list.

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 provides an explicit 'When to use' condition ('when a person asks to start watching a product') and a prerequisite ('Resolve the product first if you were given a name rather than an id'). It does not explicitly name alternative tools or state when not to use it, but the context is clear enough.

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