Skip to main content
Glama

Read a public page

read_public_page
Read-only

Reads one public nake.si HTML page by path, strips script tags, caps text at 4,000 characters, and blocks requests to other hosts.

Instructions

Read one public HTML page on https://nake.si/ only. path must start with /. Any other host is rejected before a request is sent. script tags are removed and the text is capped at 4000 characters.

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": {
      "path": "<path>"
    },
    "name": "read_public_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesA path that starts with /, such as /. Absolute URLs on other hosts are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: script tags are stripped, output text is truncated at 4000 characters, and host validation happens before any network request. It doesn't cover redirect handling or error response shape, keeping it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, zero filler, with the host restriction front-loaded before the sanitization details. Every sentence conveys distinct operational information.

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 partly compensates by describing the returned text (script tags removed, 4000-character cap). For a single-parameter read tool with annotations, that is nearly sufficient; only the failure/error response shape is left unspecified.

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 description coverage is 100% and the schema already states the path must start with / and that absolute URLs on other hosts are rejected. The description restates essentially the same constraint, so it adds little parameter meaning beyond the structured field; baseline 3 applies.

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

Purpose5/5

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

States a specific verb (read), resource (one public HTML page), and hard scope (https://nake.si/ only). An agent can immediately tell this fetches a single page rather than a site summary, distinguishing it from get_site_overview.

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

Usage Guidelines4/5

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

Gives clear acceptance conditions: path must start with /, and any other host is rejected before a request is sent. It doesn't explicitly say when to pick this over a sibling, but the scope constraint makes the appropriate use case unambiguous.

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

Deploy Server

Other Tools