Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Near-duplicate page clustering

seo-content_near-duplicate-detect
Read-onlyIdempotent

Cluster near-duplicate pages with Jaccard similarity on token shingles and connected-component clustering. Price $0.03 USDC. POST /api/v1/seo-content/near-duplicate-detect. An unpaid call returns the x402 payment terms and does not run.

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": {
      "pages": "<pages>"
    },
    "name": "seo-content_near-duplicate-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYespages, array. Required.
thresholdNothreshold, number, from 0 to 1. Required.
shingleSizeNoshingleSize, integer, from 1 to 10. Required.

Output Schema

NameRequiredDescriptionDefault
pairsNopairs. Array.
sourcesNosources. Array.
clustersNoclusters. Array.
excludedNoexcluded. Array.
singletonsNosingletons. Array.
limitationsNolimitations. Array.
shingleSizeNoshingleSize. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-schema behavior: a $0.03 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing. It stops short of describing cost/scale limits or runtime expectations, which matter for a paid clustering job.

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 short sentences, front-loaded with the operation and method, then payment and endpoint details. No filler, and the most important constraint (unpaid calls do not run) is stated compactly.

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?

An output schema exists, so return values need not be explained, and the schema fully covers inputs. The description closes the biggest non-obvious gap for an agent (paid invocation via x402). It is only slightly incomplete on when to prefer this over sibling analysis tools and on any input-size or performance caveats.

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 all three parameters (pages, threshold, shingleSize) are already documented with types and bounds. The description names the underlying similarity and shingling concepts but gives no practical meaning for threshold values or the id/html/text item tradeoff, so it adds little 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?

States a specific verb and resource ('Cluster near-duplicate pages') plus the method (Jaccard similarity on token shingles, connected-component clustering). This is precise enough to separate it from siblings like heading-outline-compare or topic-coverage-score, which operate on different signals.

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

Usage Guidelines2/5

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

There is no guidance on when to reach for this tool versus a sibling, nor on how to choose a threshold or shingle size. The only conditional statement is about payment, not about task selection, so the agent must infer usage entirely from the name and method.

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