Skip to main content
Glama

takedown

by net.lawyerd

Preserve a page as evidence

preserve_evidence
Idempotent

Preserve a public web page as evidence BEFORE it disappears: a forensic-grade package — full-page screenshot, raw and rendered HTML, HTTP headers, hosting/registrar context, SHA-256 hashes of every artifact, an OpenTimestamps Bitcoin anchor and an Internet Archive snapshot — delivered to the USER'S OWN email in ~2 minutes (free: 3/day, 10/month per email). Use when the user wants to "save proof", "screenshot for court" or fix a scam/infringing page before takedown. Sends one email to the address given; captures only public pages (no logins/paywalls); lawful preservation only. Not notarization — Lawyerd counsel can add a signed declaration of the capture procedure on request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe public page URL to preserve
nameNoRequester's name (appears in the capture record)
emailYesThe USER'S OWN email — the evidence package is delivered there
companyNoCompany or the work being protected

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
acceptedYes
nextStepYes
captureIdYes
errorCodeYes
deliveredToYes
alreadyCapturedYes
verificationUrlYes
whatHappensNextYes

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: email delivery, ~2 min duration, rate limits (3/day, 10/month), content captured, and lawful use. No contradictions with annotations.

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?

The description is concise (3 sentences), front-loaded with key action, and each sentence provides essential information without unnecessary detail.

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 the complexity (4 params, output schema, annotations), the description covers purpose, usage, behavioral traits, constraints, and delivery mechanism comprehensively. Output schema handles return value details.

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% with good parameter descriptions. The tool description reinforces that email must be the user's own but adds little additional meaning beyond schema. Baseline 3 is appropriate.

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 clearly states the tool preserves a public web page as forensic evidence, listing specific outputs and use cases. It distinguishes from siblings (assess_takedown, resolve_host, start_takedown) by focusing solely on evidence capture.

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?

The description explicitly tells when to use ('save proof', 'screenshot for court', fix scam pages) and provides exclusion (lawful preservation only, public pages only). It does not directly name sibling alternatives but context implies appropriate use.

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

All takedown toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a distinct purpose: assess_takedown analyzes the process, resolve_host finds the host, and start_takedown provides the initiation link. There is no ambiguity or overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: assess_takedown, resolve_host, start_takedown. No mixing of conventions.

Tool Count5/5

Three tools is well-scoped for a server focused on takedown-related operations. Each tool adds clear value without redundancy.

Completeness4/5

The tools cover the main workflow: host resolution, process assessment, and initiation. A minor gap is the lack of a tool to track or manage ongoing takedowns, but the server explicitly notes it files nothing, making the surface reasonable.

Resources