SteadyFetch

fetch_url

Fetch a URL with full reliability — retry, circuit breaker, cache, and anti-bot bypass.

Returns both raw HTML and clean markdown. Automatically retries on failure
with exponential backoff, falls back to plain HTTP if browser fetch fails,
and circuit-breaks domains that are consistently down.

Args:
    url: The URL to fetch
    use_cache: Whether to use cached results (default: true, TTL 1 hour)
    js_render: Whether to render JavaScript (default: true, disable for speed)
    wait_for: CSS selector to wait for before capturing (e.g., '.results-loaded')

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`wait_for`	No
`js_render`	No
`use_cache`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the transparency burden. It discloses retry with exponential backoff, HTTP fallback, domain circuit-breaking, cache TTL, and default js_render behavior. This is rich behavioral detail beyond what schemas or annotations could convey.

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 well-structured, leading with a punchy summary of capabilities and reliability, followed by a clear Args list. Each sentence adds value; no fluff or redundancy. Length is appropriate for the tool's complexity.

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?

Given the tool's complexity (4 params, no annotations), the description covers purpose, parameter semantics, reliability behaviors, and return content (raw HTML + markdown). An output schema exists but the description still provides sufficient context for an agent to invoke the tool 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 description coverage is 0%, so the description compensates with an explicit Args block explaining each parameter, including defaults and examples (e.g., wait_for CSS selector). This fully clarifies the meaning and usage of all four parameters.

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 clearly states the tool fetches a URL with full reliability, returning both raw HTML and clean markdown. It distinguishes itself from the sibling fetch_markdown by offering both formats and adding reliability features like retry, circuit breaker, and anti-bot bypass.

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?

The description provides context on when to tweak parameters (e.g., disable js_render for speed) but does not explicitly contrast with sibling fetch_markdown or explain when to prefer one over the other. It implies usage through feature listing but lacks clear exclusion or alternative guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SteadyFetch tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

fetch_url and fetch_markdown both fetch URLs, but fetch_url returns raw HTML+markdown while fetch_markdown returns only markdown, which is a clear distinction. check_domain, cache_stats, and clear_cache are all distinct. The overlap is minor and well-handled by descriptions.

Naming Consistency4/5

Most tools use a verb_noun pattern: check_domain, clear_cache, fetch_markdown, fetch_url. cache_stats deviates slightly, being a noun_noun phrase, but it's still clear and consistent enough.

Tool Count5/5

With 5 tools, the set is well-scoped for a fetch/cache utility. Each tool serves a distinct purpose without redundancy or bloat.

Completeness5/5

The tool surface covers the core lifecycle: fetching with two output formats, cache inspection, cache clearing, and domain health checks. No obvious gaps for the stated purpose of reliable fetching with caching and circuit breaking.

Resources

Need Help?