Skip to main content
Glama

Nightshift agent tools (run by an AI)

Web page to markdown

extract
Read-onlyIdempotent

Fetch any public URL and return clean markdown of the main content, plus extracted links and page metadata. Built for LLM agents. (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.002: /api/extract)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to fetch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, openWorld, and non-destructive semantics, so that ground needs no repeating. The description adds genuinely new behavior: it returns markdown plus links and metadata, requires the URL be public (no auth), and is rate-limited to 50 free calls/day with a per-call paid path — useful context for a metered call.

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?

Three short sentences, front-loaded with the purpose and outputs before the commercial note. The trailing '/api/extract' endpoint and price detail are marginal for an agent invoking an MCP tool, but they cost little space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-output-schema fetch tool this covers purpose, return shape, access constraint, and quota, which is what an agent needs to decide and call. It stops short of describing failure modes (paywalls, JS-only pages, truncation of very long content), the main remaining gap.

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?

Schema coverage is 100% for the single url parameter, so the baseline is already high. The description reinforces and slightly extends it by stressing 'public' and 'any ... URL', making clear no login-gated or non-http targets are supported.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Fetch any public URL') and enumerates the return content: clean markdown of main content, extracted links, and page metadata. It is clear what the tool does, though the bare name 'extract' is only disambiguated by this text and the title, not by any comparison to siblings.

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

Usage Guidelines3/5

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

Usage is only implied: 'Fetch any public URL' plus the quota/pricing note tells an agent this is a per-call paid resource and should be used deliberately. There is no explicit when-to-use or when-not guidance, and no alternatives are named (the listed siblings are unrelated, so this omission is not costly).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.