Skip to main content
Glama

Read a web page

stork_scrape
Read-only

Read a public web page and return its main content as Markdown for a provided https URL, optionally guided by an objective and capped by a token limit.

Instructions

Read one public web page. Returns the page's main content as markdown for a given address. The page is fetched by a page-reading provider (Firecrawl today), which is named in the reply's via field. The page is third-party content.

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": "stork_scrape"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull address of the page, starting with https://.
objectiveNoOptional: what you want from the page.
max_result_tokensNoCap on the size of the reply. Default 3000, at most 6000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, not destructive), yet the description adds real value: it names the fetching provider, discloses the `via` reply field, and warns that the page is third-party content. Auth, rate limits, and failure modes remain unmentioned, keeping it below a 5.

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?

Four short sentences, front-loaded with the action and return type, then provider and content-provenance notes. Slightly scattered (the provider sentence and the third-party caveat could be merged), but nothing is wasteful.

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 carries return-value burden and does so by stating markdown main content and the `via` field. For a simple single-URL read tool this is nearly complete; only error behavior and the token-cap interaction are left to the schema.

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?

Schema coverage is 100%, so url, objective, and max_result_tokens are already fully documented in the schema. The description adds only "for a given address" and no constraints or formats beyond that, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Read") and resource ("one public web page"), plus the return format (markdown main content), which lets an agent separate it from retrieval-style siblings like stork_search or stork_docs. It stops short of naming an alternative, so differentiation is inferred from scope rather than stated.

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

Usage Guidelines3/5

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

"Read one public web page ... for a given address" implies you must already hold a URL, which is useful context. However, there is no explicit when-to-use/when-not guidance and no routing to stork_search or other siblings, so the agent must infer selection criteria.

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