Skip to main content
Glama
Second Read

Second Read

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TAVILY_API_KEYNoWeb search key.
SECONDREAD_FAKENoSet to 1 for demo mode: no keys, no model calls.
ANTHROPIC_API_KEYNoAnthropic model key.
SECONDREAD_ENV_FILENoPath to a .env file to load; otherwise the server reads .env from its working directory.
SECONDREAD_MAX_WORDSNoDocument size cap (default 20000).20000
SECONDREAD_MODEL_MIDNoOverride the model used for the mid tier.
SECONDREAD_MODEL_CHEAPNoOverride the model used for the cheap tier.
SECONDREAD_MODEL_STRONGNoOverride 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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 content (the text or markdown) or url (a public page). Reviews take a few minutes.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

`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.

Tool Count3/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues