ScorpTech x402 API

Keyword Extract

keyword_extract

Read-onlyIdempotent

Keyphrase extraction for tagging, SEO and RAG metadata: RAKE (rapid automatic keyword extraction: candidate phrases split at stopwords/punctuation, scored by word degree / frequency) or TextRank (co-occurrence graph + PageRank, adjacent top words merged into phrases). Returns ranked multi-word phrases with score, relative relevance, occurrence count and first offset. Offline, deterministic, English stopword list (add your own); 200 KB input. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/keyword-extract

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": {
      "text": "<text>"
    },
    "name": "keyword_extract"
  }
}

Input Schema

Name	Required	Description	Default
`top`	No	Number of phrases
`text`	Yes	Text to analyse
`method`	No	rake (phrase-oriented) or textrank (graph-based)	rake
`maxWords`	No	Longest phrase in words
`minCount`	No	Drop phrases seen fewer times
`stopwords`	No	Extra stopwords (lowercase)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that extraction is offline and deterministic, includes an English stopword list that can be extended, enforces a 200 KB input limit, and charges $0.002 USDC per successful call via x402 on Solana. It also lists the returned fields, giving an agent important behavioral and operational context.

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 description is front-loaded with purpose and method choice, and every section is relevant. It is dense with parenthetical algorithm details and operational payment/endpoint information, but still reasonably concise for a paid multi-parameter tool.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description enumerates the ranked phrase fields returned: score, relative relevance, occurrence count, and first offset. Combined with the fully documented input schema and safety annotations, the definition gives an agent everything needed to select and invoke the tool correctly.

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 useful meaning by explaining RAKE candidate splitting/scoring and TextRank graph mechanics. It also clarifies stopword customization and the input-size limit, though it does not elaborate on top, maxWords, or minCount beyond the schema.

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 states a specific verb and resource: keyphrase extraction for tagging, SEO, and RAG metadata. It also names and explains the two extraction methods, making it easy to distinguish from generic text tools and siblings such as entity_extract or summarize_extractive.

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?

It gives clear use cases (tagging, SEO, RAG metadata) and explains how to choose between RAKE and TextRank. It does not explicitly name alternatives or when not to use this tool, so it falls short of the top score for usage guidance.

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

All ScorpTech x402 API tools Inspect

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

Need Help?