Skip to main content
Glama
Sign In

ScorpTech x402 Tools

by com.it.scorptech
OverviewDiscussionsAdmin

Summarize Extractive

summarize_extractive
Read-onlyIdempotent

Extractive summary with TextRank (Mihalcea & Tarau 2004): sentences are split (abbreviation / initial / decimal aware), linked by stemmed content-word overlap, ranked with PageRank, and the top N are returned in original order. No LLM, no hallucination: every summary sentence is verbatim from the input, with its index, score and offset. Choose a sentence count or a ratio. Offline, deterministic; 200 KB input. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/summarize-extractive

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

Input Schema

NameRequiredDescriptionDefault
textYesText to summarise (English works best)
ratioNoKeep this fraction of sentences instead (overrides sentences)
sentencesNoSentences to keep

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond annotations: describes the exact algorithm, that output sentences are verbatim with index, score, and offset, and mentions pricing and an HTTPS endpoint. The annotations (readOnly, idempotent) are consistent and the description adds rich 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 the core purpose and algorithm details. It includes some extra information (price, HTTPS endpoint) that may be less critical for tool selection, but every sentence still carries relevant context.

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?

Complete for an extractive summarizer: it explains the algorithm, output format (verbatim sentences with index/score/offset), input limit, determinism, and pricing. No output schema exists, but the description fully covers return value semantics.

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%, so the schema already documents each parameter. The description only adds 'Choose a sentence count or a ratio,' which is marginally helpful but not beyond what the schema provides.

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?

State a specific verb ('summarize') and resource ('extractive summary') with the exact algorithm (TextRank) and key constraints. It clearly distinguishes itself from abstractive summarizers by stating 'No LLM, no hallucination' and verbatim sentence output.

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?

Provides clear selection guidance: 'Choose a sentence count or a ratio.' It also states offline/deterministic behavior and input limit, but does not explicitly compare to alternative tools or specify when not to use it.

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

All ScorpTech x402 Tools 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