SteadyFetch

fetch_markdown

Fetch a URL and return clean markdown text optimized for LLM consumption.

Same reliability as fetch_url but returns only the markdown content,
stripping HTML, scripts, and noise. Best for when you need the page
content for analysis, summarization, or data extraction.

Args:
    url: The URL to fetch
    use_cache: Whether to use cached results (default: true)
    wait_for: CSS selector to wait for before capturing

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations provided, the description itself must disclose behavioral traits. It explains that the tool strips HTML, scripts, and noise to produce clean markdown, and the args section details caching and wait behavior. However, it does not mention potential errors, redirects, rate limits, or side effects, leaving some behavioral aspects undisclosed.

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 concise and well-structured: a clear opening sentence, a comparative sentence, and an args block with each parameter explained. Every sentence adds value with no redundancy, and the most important information is front-loaded.

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?

Given the tool's moderate complexity, the description covers purpose, usage guidance, and all parameters. With an output schema present, return values need not be detailed. It lacks some edge-case context like error handling or cache invalidation, but the core decision-making information is present.

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?

Since schema description coverage is 0%, the description fully compensates by explaining each parameter: url is 'The URL to fetch', use_cache is 'Whether to use cached results' with default true, and wait_for is 'CSS selector to wait for before capturing'. This adds meaningful semantics beyond the bare schema definitions.

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 and returns clean markdown text. It also differentiates from the sibling fetch_url by noting it returns only markdown content and strips HTML, scripts, and noise, making its purpose specific and distinct.

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 explicit usage context: 'Best for when you need the page content for analysis, summarization, or data extraction.' It also references the alternative fetch_url, implying when to use this variant. However, it does not explicitly state when not to use it or list alternatives beyond mentioning fetch_url.

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?