Second Read
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAVILY_API_KEY | No | Web search key. | |
| SECONDREAD_FAKE | No | Set to 1 for demo mode: no keys, no model calls. | |
| ANTHROPIC_API_KEY | No | Anthropic model key. | |
| SECONDREAD_ENV_FILE | No | Path to a .env file to load; otherwise the server reads .env from its working directory. | |
| SECONDREAD_MAX_WORDS | No | Document size cap (default 20000). | 20000 |
| SECONDREAD_MODEL_MID | No | Override the model used for the mid tier. | |
| SECONDREAD_MODEL_CHEAP | No | Override the model used for the cheap tier. | |
| SECONDREAD_MODEL_STRONG | No | Override the model used for the strong tier. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_documentA | Review a document draft with a desk of specialist agents: a fact-checker that cites sources, a devil's advocate that builds the strongest counter-case, a structure reviewer, a copy editor and an originality check. Returns a markdown report (must fix, counter-case, should fix, polish, originality notes, claim ledger). Pass exactly one of |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With a single tool there is no possibility of misselection; the tool's purpose (multi-perspective document review) is stated explicitly and unambiguously. The input contract (exactly one of `content` or `url`) and the report shape are spelled out, leaving no room for a competing interpretation.
`review_document` follows a clean verb_noun snake_case pattern that describes exactly what it does. There are no other names to clash with or deviate from.
A one-tool server is inherently thin against the 3-15 sweet spot, even though the single tool internally bundles several specialist reviewers. It works as a focused capability, but there is no granularity — you cannot invoke just the fact-checker or just the copy editor.
The tool covers the core end-to-end review workflow (fact-check, counter-case, structure, copy edit, originality) and returns a structured markdown report, so the primary job is done. Minor gaps exist: no way to re-run a targeted subset of reviewers, iterate on a revised draft, compare versions, or retrieve a past report.