Skip to main content
Glama
kubainter

BoteX

by kubainter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

fetch_url

Fetch one public http(s) text document for caller-side research.

Instructions

Fetch one public http(s) text document for caller-side research.

This tool is intentionally separate from BoteX's internal read_url: the
orchestrating agent chooses the URL, so arbitrary public hosts do not have
to be configured in net.allowed_hosts. SSRF protections, redirect
revalidation, content-type checks, byte limits, and secret masking still
apply. In net.policy='allowlist', only configured hosts may be fetched.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
max_bytesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses SSRF protections, redirect revalidation, content-type checks, byte limits, secret masking, and the allowlist-mode restriction. This is unusually rich behavioral context for a no-annotation tool.

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-loads the core purpose in the opening clause and keeps the security model tight across a few sentences. Every sentence adds distinct information, though the prose could be marginally denser.

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?

An output schema exists, so return values need not be explained, and the security/policy model is well covered. The remaining gap is the undocumented max_bytes parameter, which leaves an agent guessing about truncation behavior.

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

Parameters2/5

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

Schema description coverage is 0% and there are two parameters, so the description must compensate. It adds some meaning to 'url' via 'public http(s) text document', but never explains max_bytes (default 0 presumably means unbounded) or its interaction with the byte limits it mentions.

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 and resource ('Fetch one public http(s) text document') plus the calling context ('caller-side research'). It explicitly distinguishes itself from BoteX's internal read_url, so an agent can tell the two apart without opening a schema.

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

Usage Guidelines4/5

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

Explains why this tool exists (the orchestrating agent chooses the URL, avoiding allowlist configuration) and gives the selecting condition for the alternative (internal read_url). It also notes the net.policy='allowlist' restriction. It stops short of an explicit when-not/exclusion statement beyond that policy note.

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