Skip to main content
Glama
Sign In
Kloakt

Kloakt

by KultMember6Banger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

kloakt_fetch

Fetch web pages with JavaScript rendering, returning raw output as HTML, text, links, markdown, or custom JavaScript evaluation. Supports stealth anti-detection.

Instructions

Low-level page fetch with JS rendering. Returns raw output as string. Supports HTML dump, text dump, link extraction, or arbitrary JS evaluation.

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": "kloakt_fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to fetch
dumpNoOutput format (default: text)text
eval_jsNoJavaScript expression to evaluate on the page
stealthNoEnable anti-detection mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, description discloses JS rendering and raw string output, but does not address potential side effects of eval_js or stealth mode behavior.

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?

Two concise sentences front-load purpose and cover key features without redundancy.

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?

Covers main functionality and return format, but lacks details on eval_js output handling and stealth mode implications; adequate for a fetch tool.

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?

100% schema coverage; description aligns with parameters but adds no meaningful new details beyond the schema's own descriptions.

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?

Description clearly states 'low-level page fetch with JS rendering' and lists supported output formats, distinguishing it from sibling tools like kloakt_extract or kloakt_scrape.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives; only implies it's for raw fetching without context from sibling descriptions.

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