list_watchesList the member's saved monitors and recent matches. Requires member authorization with watches:read and an active Founding Pro entitlement.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond annotations by specifying the authorization requirement (watches:read) and the active Founding Pro entitlement prerequisite, which are not present in the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no wasted words. It front-loads the core action and object, then adds the essential access prerequisite. Every sentence contributes actionable information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only listing tool, the description fully covers what is listed, who it belongs to, and the auth/entitlement conditions required. With no output schema present, the description still communicates the return scope—'saved monitors and recent matches'—which is sufficient for an agent to understand the tool's purpose and invocation constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and 100% schema description coverage, so there is no parameter documentation burden on the description. The description's mention of 'the member' aligns with the implicit authorization context rather than any parameter, which is appropriate for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb and resource: 'List the member's saved monitors and recent matches.' It distinguishes itself from sibling tools like create_watch and update_watch by framing this as a read-only listing operation. The title reinforces the object being listed, Founding Pro saved watches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when the tool is appropriate: it lists the member's saved monitors and recent matches, and it explicitly calls out the required authorization scope and entitlement. It does not explicitly name alternatives or exclusions, but the read-versus-write contrast with siblings is clear enough for an agent to select this tool for listing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The watch and edition tools are clearly distinct, but get_context and score_headline overlap heavily—both accept a headline, share the referenceContext parameter, and disclose withheld/conflicting info—and get_brief vs read_latest_edition both serve 'what's the latest news' requests. The verbose 'do not use for' guardrails in the descriptions help, but they also signal that the boundaries are not naturally obvious.
All names follow snake_case verb_noun, with predictable patterns: list_* for collections, create/update/acknowledge for watch mutations, read_* for editions. Minor inconsistency exists between get_brief and read_latest_edition (both fetch news content) and between get_membership and list_watches (both return list-like info), but the overall scheme is readable and consistent.
14 tools sits within the typical well-scoped band, and each tool appears to serve a real product feature. The surface is slightly broad for a 'news' server, spanning saved-watch management, edition reading/export, headline analysis, and membership/checkout, which makes it heavier than a focused news reader.
Edition access (list/read/export) and the analysis workflow (score/context/discover) are well covered, but the watch lifecycle has no delete_watch, leaving agents unable to remove saved watches—a real dead end. There is also no story-level read or search tool, though the descriptions explicitly scope that out.