export_editionExport an edition as source-grounded Markdown or CSV. Requires member authorization with exports:read and an active Founding Pro entitlement.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | ||
| format | No | ||
| category | No | Only return replacements in this category. |
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 declare read-only, idempotent, and non-destructive behavior. The description adds useful context beyond annotations: the authorization requirement ('exports:read') and the Founding Pro entitlement, plus the source-grounded nature of the output.
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?
A single front-loaded sentence states the core action and formats, then adds the key prerequisite. There is no filler or redundant repetition of the title.
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?
The definition is adequate for basic invocation: format and category are inferable from the enum and schema description, and date follows from the edition context. However, with no output schema and all parameters optional, it does not explain default behavior (e.g., what happens with no date) or the exact return form.
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?
Schema description coverage is only 33%, so the description needed to clarify parameter meaning but only conveys format values ('Markdown or CSV'). The 'date' parameter has no semantic explanation, and 'category' is only documented in the schema, not the description.
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 states a specific action ('Export an edition') with a clear resource and output formats ('source-grounded Markdown or CSV'). It also distinguishes itself from sibling read/list tools by requiring exports:read and an active Founding Pro entitlement.
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?
Usage is implied: use this tool when a serialized Markdown or CSV export is needed, rather than reading an edition in-app. However, the description does not explicitly name alternatives like read_edition_by_date or state when not to use this tool.
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.