Skip to main content
Glama

List watched products

watchlist.list
Read-onlyIdempotent

Return the watchlist of the one Founding Pro account this key is bound to, with each product's monitoring state.

When to use: Use to answer what a person is watching, when each product was last read, when the next check is due, and whether anything is currently unreadable.

What it cannot provide: It reaches exactly one account, the one bound to this key, and no other. It returns no candidate detail, no source URL and no internal identifier, and it is not a way to read the covered set.

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

No arguments

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

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

Beyond annotations (readOnly, openWorld=false, idempotent), the description discloses the single-account scope, daily read limits, enforcement consequences ('refused, scored, and can suspend the key'), and the meaning of statuses as Record states rather than facts about products. It also warns against misusing coverage or treating observation dates as reformulation dates.

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 longer than average but front-loaded with the primary purpose and organized with clear sections: 'When to use', 'What it cannot provide', 'Limits', and status interpretation. It is dense rather than padded, though a few warnings could be tightened without losing value.

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?

For a parameterless, read-only list tool with an output schema and annotations, the description covers account binding, daily limits, prohibited iteration, status semantics, date semantics, and non-medical scope. Nothing needed to decide whether and how to call it is missing.

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?

The input schema has zero properties, so there are no parameter semantics to document. The description appropriately adds no parameter details and avoids inventing arguments; baseline 4 applies for parameterless tools.

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 the watchlist of the one Founding Pro account this key is bound to, with each product's monitoring state.' It also distinguishes itself from siblings by stating what it cannot provide, such as candidate detail, source URLs, and internal identifiers, and by framing itself as the list operation rather than a coverage read.

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?

There is an explicit 'When to use' block listing concrete questions the tool answers: what a person is watching, last read times, next check due, and unreadable items. The 'What it cannot provide' and 'Limits' blocks add exclusions, but the description does not name a specific sibling tool as the alternative, so it stops short of fully routing the agent.

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