Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Map a site

map
Read-onlyIdempotent

List a website's URLs (sitemaps + the start page's links), optionally ranked by a search phrase. 1 credit; free when nothing is found.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
limitNo
searchNoKeep only URLs relevant to these words, most relevant first; with a thin sitemap it also reads up to 8 linked pages one level deeper
exclude_pathsNoRegular expressions; drop URL paths matching one
include_pathsNoRegular expressions; keep only URL paths matching one (e.g. ^/docs/)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Keep only URLs relevant to these words, most relevant first"New value: +"Keep only URLs relevant to these words, most relevant first; with a thin sitemap it also reads up to 8 linked pages one level deeper"
  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 cover safety (readOnly, idempotent, non-destructive), so the description's job is extra context — and it delivers cost ('1 credit; free when nothing is found') and mechanism (sitemaps + start page links), which tells the agent the result set is bounded by what the site exposes. It doesn't mention pagination or result ordering beyond the optional search ranking.

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 short sentences, both front-loaded: the scope and data source come first, the credit caveat second. No filler or restatement of the title.

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?

For a read-only, single-required-parameter tool with no output schema, the description conveys what is returned (URLs), where they come from, and the billing model. The only real gap is the unexplained limit parameter and how results are ordered absent a search phrase.

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 60%, with search, exclude_paths and include_paths self-documented in the schema. The description reinforces the search-ranking behavior but adds nothing for 'limit' (cap 5000) or the path-filter regexes, so it does not fully compensate for the documented gap.

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 ('List a website's URLs') plus a precise scope: sitemaps plus the start page's links. That distinguishes it from navigation-style siblings like search or webpage, though it never names crawl, which is the nearest alternative for follow-up content fetching.

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?

'Optionally ranked by a search phrase' implies a discovery use case, but the description never states when to use map versus crawl, search, or extract, and gives no exclusions. The agent must infer the routing decision from sibling names alone.

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