Skip to main content
Glama

anew

by page.anew
OverviewDiscussionsAdmin

Read a page (anew.page URL → its HTML source)

anew_read
Read-only

Pass an anew.page URL, get back the HTML document encoded in it, plus its canonical URL and byte size. (Two in-page tools share this name and take no arguments: the editor's reads the document open in the editor, and a rendered page's reads the page being viewed. This one takes a url and reads that page.) To revise an existing anew page, its URL is its source: read it, edit that HTML, write it again. The new URL is a separate page and the original keeps working. Read returns the author's exact bytes — no anew-injected tags, no proxied image srcs — so it re-encodes byte-for-byte. Never re-author from a rendered page, a scraped DOM, or a screenshot: each loses the author's markup, and none is faster than reading the slug. Decoding is local and exact, so any anew URL reads — the page needs no prior visit and no fetch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAn anew.page URL, or a bare slug. Subdomain, cosmetic-prefix and #hash forms all resolve.
formatNoHow the document rides back. "text" (default) is one plain text block. "resource" is one embedded-resource block ({type:"resource"}, mimeType text/html) — the typed MCP form for callers that want the page tagged as HTML rather than loose text. Same bytes both ways.text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical anew.page URL for this document.
bytesYesEncoded URL length in bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / limit
      Removed value: -{
-  "description": "Unfurl-safe URL threshold (4000); headroom = limit - bytes. Past it the URL still works (hard ceiling 65000), it may just break in some apps.",
-  "type": "integer"
-}
    • changedOutput schema / required
      Previous value: -[
-  "url",
-  "bytes",
-  "limit"
-]New value: +[
+  "url",
+  "bytes"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real beyond-annotation context: decoding is local and exact, no prior visit or fetch needed, returns the author's exact bytes with no anew-injected tags and byte-for-byte re-encoding. It does not fully explain the idempotentHint=false nuance, but the behavioral substance is well above the annotation baseline.

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

Conciseness4/5

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

Front-loaded with the core action and return values, followed by the disambiguation parenthetical and the re-authoring guidance. Dense and mostly every sentence earns its place, though the digression about the two same-named in-page tools is longer than strictly needed.

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?

Given an output schema exists (so return values need not be re-explained) and annotations cover safety, the description supplies exactly the missing pieces: disambiguation from same-named siblings, the round-trip editing workflow, and the exact-bytes/local-decode guarantees. Complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters (url, format) carry detailed schema descriptions covering slug/subdomain/hash forms and the text vs resource distinction with the same-bytes guarantee. The description adds context that URL is the canonical source but adds no parameter syntax beyond the schema, so baseline 3 is correct.

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?

Front-loads a precise verb+resource: 'Pass an anew.page URL, get back the HTML document encoded in it, plus its canonical URL and byte size.' It explicitly resolves the name collision with two sibling in-page tools that share this name, and names the counterpart anew_write for revisions. An agent can distinguish this from anew_editor/anew_page/anew_write without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (read, edit, write back for revisions; any anew URL reads with no prior visit) and when-NOT-to (never re-author from a rendered page, scraped DOM, or screenshot). It routes against alternative input sources explicitly rather than leaving it to inference.

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

All anew toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources