Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Top keywords of a public web page

text_keywords
Read-only

Extract top keywords and word frequencies from a web page URL. Keyword extractor for a public web page: top terms and word frequency counts from the page text (respects robots.txt). Deterministic, no AI, no API key. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/text/keywords

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world safety, and the description adds genuinely useful behavior: deterministic output, no AI/no API key dependency, robots.txt compliance, and a per-call price of $0.001 USDC via x402 on Base. It does not describe what happens when a URL is blocked or unreachable, nor the shape of the returned ranking, but the cost and determinism disclosures are the key operational facts an agent needs before paying for a call.

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 definition front-loads the action in the first sentence and keeps supporting traits in one compact block, with no redundant restatement of the title. The pricing figure and demo URL are slightly promotional, but price is decision-relevant for a paid x402 endpoint, so the bulk of the text earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should say something about the returned structure (ranked terms plus frequency counts, and how `limit` affects it), which it does not. It does adequately cover access constraints, cost, and determinism, so the definition is workable but leaves a gap around result shape for a variable-output extraction tool.

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

Parameters2/5

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

Schema coverage is only 50%: `url` is documented as a public http(s) URL, but `limit` has no description in the schema, only min/max bounds (1-50). The description never mentions `limit`, leaving the agent to guess whether it bounds the number of returned keywords or the word count processed — a meaningful ambiguity for an extractor whose output is variable-length.

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 and resource: 'Extract top keywords and word frequencies from a web page URL.' The resource (keywords/term frequencies from page text) is clearly distinct from sibling capabilities like text_readability, web_markdown, or web_meta, so an agent can select it on the description alone.

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 context is implied rather than stated: the page must be a public http(s) URL and robots.txt is respected, which tells the agent when the tool is applicable. However, there is no explicit when-to-use vs. when-not guidance and no named alternative (e.g., text_readability for prose-level scores), so the routing burden remains on the agent.

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