Skip to main content
Glama
aidvizhhub

camoufox-research

by aidvizhhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Чтение страницы

fetch_page
Read-onlyIdempotent

Read a single web page as clean text without HTML clutter. Supports JavaScript sites, caching, and delta reading to save tokens.

Instructions

Текст страницы без HTML-мусора (статьи, доки, README). Кэш на сутки. article_only=True — текст статьи (Trafilatura), fallback — весь body. delta=True — delta-чтение: если контент не изменился с прошлого раза, вернёт маркер '[delta: ...]' вместо текста (не тратим токены на повтор). max_chars режет только ОТВЕТ, а не чтение: страница кладётся в кэш целиком (потолок 100k), поэтому повтор с большим max_chars мгновенный и бесплатный по времени (замер 21.09: asyncio-task.html = 46 094 симв. в кэше; 12000 = 26% текста, 40000 = 87%, все ответы 0.0с). КОГДА: прочитать 1 страницу (JS/SPA — тоже) чистым текстом. НЕ КОГДА: страниц 10+ → batch_fetch; нужны поля по схеме → extract; повторное чтение → delta=True; нужен клик/ввод → session_start.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
deltaNo
max_charsNo
article_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.21.1
    • changedInput schema / properties / max_chars / default
      Previous value: -6000New value: +12000
  2. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / delta
      Added value: +{
+  "default": false,
+  "title": "Delta",
+  "type": "boolean"
+}
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, but the description adds material context beyond them: a ~24h cache, how delta avoids re-emitting unchanged content, and that max_chars truncates only the response while the full page (up to 100k) is cached. That directly affects token and retry decisions.

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 purpose, then semantics, then the when/when-not routing. Dense but nearly every clause earns its place; the parenthetical benchmark measurement (21.09 timings, 26%/87% figures) is more illustrative detail than an agent strictly needs.

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?

An output schema exists so return structure needn't be documented, yet the description still explains the one non-obvious return case (delta marker). With caching, truncation, extraction fallback and sibling routing all covered, an agent has everything needed to call this correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does: it defines delta (marker instead of text on unchanged content), article_only (Trafilatura article extraction with full-body fallback), and max_chars (response-only truncation with cache reuse). Only url is left to self-evidence, which is reasonable.

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?

States a specific verb+resource (read one page as clean text, JS/SPA included) and immediately differentiates itself from siblings: batch_fetch for 10+ pages, extract for schema fields, session_start for interaction. No sibling overlap is left ambiguous.

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?

Explicit КОГДА / НЕ КОГДА block with named alternatives for each exclusion case (batch_fetch, extract, delta=True, session_start). This is the strongest form of routing guidance.

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