Skip to main content
Glama

Find the important pages of a website from its home page links

key_pages
Read-only

Find the important pages of a website from its home page links: about, contact, pricing, careers, blog, docs, login, signup, team, privacy and terms. Saves agents from crawling. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavior: a 1-3 s latency expectation, a free quota of 20 calls/day per user, and a $0.002 per-call overage billed via x402 in USDC on Base. That commercial and performance context is exactly what annotations cannot convey. It stops short of describing the return payload, which matters because there is no output schema.

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?

Three compact sentences, front-loaded with the purpose and target page list, then the value proposition, then the cost/rate model. Every clause carries information an agent needs to decide and to budget; nothing is redundant.

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 two-parameter, no-output-schema tool, the definition covers purpose, cost, latency and quota, which is the bulk of what an agent must know. The gaps are the shape of the result (page names paired with absolute URLs?) and failure modes for sites lacking home page links, which the agent cannot learn from structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: it explains why the payment parameter exists (free tier of 20 calls/day, then per-call pricing) and that payment is gasless USDC on Base. It adds nothing about the url parameter beyond what the schema's 'Public http(s) URL' already states.

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?

The description states a specific verb and resource ('Find the important pages of a website from its home page links') and enumerates the target page types (about, contact, pricing, careers, blog, docs, login, signup, team, privacy, terms), making the scope unambiguous. It does not name a sibling tool to contrast with, so it falls just short of the top band.

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?

'Saves agents from crawling' implies the use case — call this instead of fetching and parsing the home page yourself — but that is inference rather than explicit guidance. There is no statement of when not to use it or which sibling (e.g. links, broken_links) covers adjacent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.