Skip to main content
Glama
Flux MCP

Flux MCP

Official
by Flux-Search

fetch

Read-only

Fetch a full web page as clean markdown with its title and published date. Use it when you need the complete page rather than only the passages that answer a question.

Instructions

Fetch one web page and return it whole as clean markdown, with its title and published date. Use it when you need the full page; use lineage when you only need the parts that answer a question, which is cheaper on long pages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA public http or https address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds value by stating the return format and metadata fields, and by disclosing the cost trade-off on long pages. It stops short of covering failure modes an open-world fetch implies, such as paywalls, non-HTML content, or truncation on very large pages, so it is strong but not fully transparent.

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?

Two sentences, both earning their place: the first front-loads what the tool returns, the second handles routing and cost. There is no filler, no restatement of the name, and the decision-relevant clause comes last where it is easy to find.

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?

With no output schema, the description correctly takes on the burden of describing the return value in concrete terms (clean markdown, title, published date), which is what an agent needs to know. For a one-parameter read tool that is nearly complete; the only shortfall is the absence of any note on what happens when a page cannot be fetched or is unusually long, despite the cost hint.

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?

There is a single required parameter with 100% schema description coverage ('A public http or https address'), so the schema already carries the semantics. The description adds no format, encoding, or edge-case detail about the URL beyond what the schema states, which is the expected baseline for a fully documented single parameter.

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 names a specific verb and resource (fetch one web page) and states the return shape (whole page as clean markdown, plus title and published date). It also distinguishes itself from the sibling lineage by contrasting full-page retrieval against partial extraction, so an agent can choose without opening either schema.

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 gives an explicit when-to-use rule ('when you need the full page') and names the alternative tool plus the condition that selects it ('lineage when you only need the parts that answer a question'). It even supplies the deciding trade-off — lineage is cheaper on long pages — which is exactly the information an agent needs to route between the two.

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