Skip to main content
Glama
Sign In

PublicWWW

by com.publicwww
OverviewDiscussionsAdmin

PublicWWW documentation and prices

read_docs
Read-onlyIdempotent

PublicWWW's own documentation and price list, in Markdown: query syntax and operators, websites about a topic (like:), regular expressions (snipexp:), country domains, ready-made example queries, clusters and extraction, the REST API, this MCP server, site languages, plans and prices with what each plan opens. Without page or pages - the table of contents, every page with the headings inside it. Read every page that may matter at once: several ids in pages. Use it for any question about how PublicWWW works or what it costs. Spends nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the page; English by default. Pages without a translation come in English.en
pageNoLeave out page and pages to get the table of contents. Otherwise a page id from it.
pagesNoSeveral page ids at once, up to 6 - everything that may matter for the question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Page id from the table of contents, for example query-syntax/regex, api/limits or prices. Leave out to get the table of contents."New value: +"Leave out page and pages to get the table of contents. Otherwise a page id from it."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond them with 'Spends nothing', a genuinely useful behavioral fact for a credit-metered API, and clarifies that an omitted page/pages yields the table of contents. It does not say how large pages are or whether responses are truncated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The one-line topic inventory is dense but front-loads the key fact (what the tool contains) before the navigation rules. Sentences all carry information; the topic list is long but each item tells the agent whether a question is in scope, so little waste remains.

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?

Three optional parameters, no output schema, and a read-only tool: the description supplies the content inventory, the TOC-first workflow, batch-read guidance, and the free-of-charge property. The only gaps are response size and whether a fetched page can be truncated, which are minor for a documentation reader.

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 100% and the schema already explains lang, the TOC-when-omitted behavior of page, and the maxItems=6 cap on pages. The description adds only the intent behind batching ('Read every page that may matter at once'), which is marginal. Baseline 3 is appropriate when the schema carries the parameter documentation.

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?

The description names the specific resource (PublicWWW's own documentation and price list), the return format (Markdown), and the exact topics covered: query syntax, like:, snipexp:, country domains, clusters, REST API, MCP server, languages, and plans/prices. An agent can distinguish this from the data-query siblings such as search or get_cluster without opening any schema.

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?

'Use it for any question about how PublicWWW works or what it costs' plus 'Without page or pages - the table of contents' gives a clear trigger and a two-step navigation pattern (get TOC, then fetch ids). It stops short of naming an explicit alternative or exclusion - e.g. 'do not use this to run a search query' - so the routing is clear but not complete.

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

All PublicWWW 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