Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Fetch webpage

webpage
Read-onlyIdempotent

Fetch a public URL (HTML or PDF) and return its main content as clean Markdown with metadata. 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
countryNoFetch the page as seen from this country, e.g. de (geo-dependent pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"Fetch through an exit in this country, e.g. de (geo-dependent pages)"New value: +"Fetch the page as seen from this country, e.g. de (geo-dependent pages)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely new context: the transformation performed (raw page reduced to main content), the output format, and a cost of 1 credit — a pricing detail absent from all structured fields. It stops short of noting JS-rendering limits, timeouts or failure modes.

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, zero filler: the operation and its output are front-loaded, and the credit cost is appended compactly. Every clause carries information an agent would otherwise have to guess.

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 carries the return-value burden by naming the Markdown-plus-metadata shape. Combined with annotations covering side effects and openness, the definition is nearly complete; only edge-case behavior (paywalls, non-200 responses, content truncation) is unaddressed.

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 50%: country is documented in the schema while url is not. The description partially compensates by constraining url to public HTML or PDF resources, but adds nothing about URL format, redirects, or how the optional country parameter interacts with the fetch.

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 and resource (fetch a public URL) plus the return contract (main content as clean Markdown with metadata), which is far more informative than the title alone. It does not distinguish itself from close siblings like crawl or extract, so an agent must infer that this is the single-page variant.

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?

The phrase 'public URL' implicitly excludes authenticated or private pages, which is useful scoping, and the '(HTML or PDF)' note implies supported input types. However there is no explicit when-to-use guidance and no routing to alternatives such as crawl for multi-page retrieval or extract for structured fields.

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

All SerpKite toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources