Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
API_KEYNoAPI key for direct access; accepted on MCP endpoints via X-API-Key or Authorization: Bearer.
MCP_API_KEYNoOptional scoped key accepted only on MCP surfaces (/mcp, /mcp/tools, /mcp/tools/call); can be used instead of the master API_KEY for MCP connector authentication.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
bintu_scrape_textA

Fetch one public absolute HTTP or HTTPS URL and extract readable text. Only HTML/XHTML is supported, with a 1 MiB decoded-body limit and extracted text capped at 6,000 characters. Article/main content is preferred and common page furniture is omitted. Default mode=scrape returns the extraction envelope. Use mode=chunk (accepted alias: chunked) for approximately budgeted chunks, or mode=summarize for sentence-based truncation. Chunking preserves words, URLs, and recognized table rows; an intact URL, word, or table row may exceed max_tokens. Whitespace can be normalized during chunking. tokens and approx_tokens are character-based sizing estimates, not tokenizer counts or exact billing measurements. tokens_saved_estimate compares source HTML and delivered text estimates when the baseline is available; cached results may preserve the original extraction economics. Savings are not limited to summarize mode. truncated reports content truncation; split reports multiple chunks. The character cap applies before mode transformation. max_tokens is ignored in scrape mode. Set cache=false to bypass cache reads; successful fresh results may still be written to cache. JavaScript rendering is available only when enabled by the operator. If render_js_disabled is returned, retry with render_js=false. Execution failures are reported in-band with isError=true.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no risk of confusing it with another tool. Its purpose is clearly focused on fetching and extracting readable text from a URL.

Naming Consistency5/5

The sole tool name uses a clear snake_case pattern with a server prefix and an action-oriented verb. With only one tool, there are no cross-tool naming inconsistencies.

Tool Count3/5

A single tool is sufficient for a narrowly focused scraping server, and its modes add flexibility. However, one tool is thin relative to the typical multi-tool surface and may feel limited for broader web-context workflows.

Completeness4/5

The tool covers the core fetch-and-extract workflow, including scrape, chunk, and summarize modes with caching and truncation details. There are minor gaps around non-HTML content, batch URLs, and guaranteed JavaScript rendering, but these are workaroundable or explicitly scoped limitations.

Maintenance

ActivityMaintained
ResponsivenessNo issues