Skip to main content
Glama
Bristlecone2026

Bristlecone Logic Utilities

by Bristlecone2026
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

extract_web

Read-onlyIdempotent

Fetch clean, readable text from any public web page by stripping HTML, navigation, and scripts. Returns body text and HTTP status for summarization or analysis.

Instructions

Fetches and sanitizes readable text content from any public HTTP or HTTPS web page. Strips boilerplate HTML tags, navigation bars, and scripts. Returns clean body text and HTTP status code. Use when an agent needs primary webpage content for summarization or analysis. Do not use for authenticated pages or executing JavaScript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe complete target website URL including http:// or https:// protocol prefix (e.g. 'https://docs.python.org/3/').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.3
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "content": {
-      "type": "string"
-    },
-    "status_code": {
-      "type": "integer"
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "url",
-    "status_code",
-    "content"
-  ],
-  "type": "object"
-}New value: +null
  2. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful context about what gets stripped and what is returned, plus usage boundaries. However, it omits potential rate limits, timeouts, or error-handling details for non-HTML or failed requests.

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 front-loaded with purpose and output, then adds usage conditions and exclusions. Every sentence contributes directly to correct invocation without waste.

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?

With no output schema, the description carries return information (clean body text and HTTP status code) and operational boundaries. It provides enough context for an agent to call the tool correctly given its simplicity and annotation coverage.

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 the single URL parameter is fully documented in the schema. The description does not add syntax or format details beyond what the schema provides, so the baseline score of 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 states a specific verb and resource: fetches and sanitizes readable text content from public HTTP/HTTPS web pages. It clearly distinguishes the tool's output and scope, and no sibling tool performs the same operation.

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?

It explicitly says when to use it (needs primary webpage content for summarization or analysis) and when not to use it (authenticated pages or JavaScript execution). This leaves no ambiguity for selection.

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