Skip to main content
Glama
Second Read

Second Read

Review a document

review_document
Read-only

Reviews document drafts with specialist agents that fact-check claims, build counter-arguments, check structure, copyedit, and flag originality, returning a markdown report of fixes and notes.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "review_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public http(s) page to fetch and review, instead of `content`.
focusNoOptional steer, e.g. "check the financial figures".
contentNoThe document text or markdown. Give this or `url`, not both.
profileNo`auto` (detect), `opinion` (essays, op-eds, posts) or `design_doc` (technical designs and proposals).auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so safety is covered; the description adds genuine behavioral context beyond that: the multi-agent review process, the markdown report's six sections, and the multi-minute runtime. It stops short of disclosing failure modes (e.g., unreachable URL, oversized documents) or limits, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it does, what it returns, how to call it, plus a latency note. The most decision-relevant information (input exclusivity and runtime) is front-loaded and no sentence is filler.

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?

Although there is no output schema, the description enumerates the report's sections, so return values are covered. Combined with the latency disclosure and input-exclusivity rule, an agent has everything needed to invoke and interpret the tool correctly.

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?

With 100% schema description coverage the baseline is 3, but the description adds the XOR constraint between `content` and `url` that the schema only weakly implies, and reinforces the `profile` enum semantics with examples. This is meaningfully more than the structured fields alone.

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 names a specific verb and resource ('Review a document draft') and immediately differentiates itself by enumerating the five specialist reviewer roles and the exact report sections produced. An agent knows precisely what the tool does and what comes back without opening any schema.

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?

It states the mutually exclusive input rule ('Pass exactly one of `content` or `url`') and explains the `profile` values with concrete examples of when each applies. It also warns about latency ('a few minutes'), but gives no explicit exclusions or when-not-to-use guidance, which is reasonable given there are no sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools