Skip to main content
Glama

Sitesy Website Intelligence

Page links

page_links
Read-onlyIdempotent

The links on one web page, split into internal and external, with anchor text. Costs 0.002 USDC per call. The caller pays per call in USDC on Base through x402: the first call returns the payment requirements, and an x402 aware MCP client signs and retries automatically.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA web page address, for example https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, openWorld and non-destructive, yet the description adds the critical non-obvious behavior: the first call does not return links but payment requirements, and an x402-aware client must sign and retry. It also discloses the 0.002 USDC per-call cost. It stops short of describing result limits or rate/anti-bot behavior on failed fetches.

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 with no waste: the return shape comes first, then the pricing and payment handshake. Every clause carries information an agent needs before calling.

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 specifies the return shape and the payment flow an agent must handle. Only minor gaps remain, such as what happens on an unreachable or non-HTML page.

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 parameter already fully documented in the schema with format and an example (schema coverage 100%). The description adds no meaning beyond that, which is the expected baseline here.

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?

Names the exact resource (links on one web page) and the shape of the result (internal vs external, with anchor text), which separates it from page_reader and page_metadata. It is a noun phrase without an explicit verb, so it is clear but not maximally directive.

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?

Usage is only implied by the described output — an agent must infer that this is the tool to pick when it wants link inventory rather than page text. No alternatives or exclusions are named, though the payment-retry note does give practical invocation guidance.

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.

Resources