Skip to main content
Glama

Semerenko Group Public Site MCP

Find related content and internal-link targets

sem.find_related
Read-only

Given a topic, draft title, or existing URL, returns the most relevant existing public pages ranked by a 0-1 relevance score, each tagged duplicate_risk (link or update instead of writing new), related (good internal-link target), or weak. Top-level recommendation says whether to write new or consolidate. Use this BEFORE writing new content to avoid cannibalization and to pick internal links. Title/keyword/category scoring only - no external calls, no AI cost.

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": "sem.find_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional existing Semerenko URL; its title and excerpt seed the topic and it is excluded from results.
typeNoOptional content-type filter. Default "any".
limitNoMaximum related pages to return. Default 10.
topicNoTopic, keywords, or draft title for the content you intend to write. Required unless "url" is given.

Output Schema

NameRequiredDescriptionDefault
topicNo
resultsNo
recommendationNo
duplicateRiskUrlNo
suggestedInternalLinksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered; the description adds real context beyond that: scoring is limited to title/keyword/category, there are no external calls and no AI cost, and the URL parameter case excludes that page from results. It does not discuss result count behavior or ranking ties, but the substantive behavioral disclosure is present.

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?

Three compact sentences, front-loaded with what is returned before the tagging scheme and the usage directive. Dense but every clause carries information; only the trailing "no external calls, no AI cost" clause is mildly redundant with the openWorldHint annotation.

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?

With an output schema present, the description needn't detail return values, yet it still explains the tag taxonomy and the top-level recommendation, which is the part an agent must interpret when deciding to write or consolidate. Combined with full schema coverage and read-only annotations, nothing needed to call it correctly is missing.

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 four parameters are already documented in the schema, including the url-exclusion and topic-required-unless-url rules. The description reinforces the topic/URL duality ("topic, draft title, or existing URL") but adds no format or syntax detail beyond what the schema supplies, so the baseline 3 applies.

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: given a topic, draft title, or URL, return the most relevant existing public pages ranked by a 0-1 relevance score, each tagged duplicate_risk, related, or weak. The three tag meanings and the top-level write-new-vs-consolidate recommendation make the output shape concrete enough to distinguish it from list/search siblings.

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 this BEFORE writing new content to avoid cannibalization and to pick internal links" gives a clear triggering context and a stated goal. It stops short of naming an explicit alternative (e.g., sem.search_content) or when-not-to-use conditions, so it is strong but not complete routing guidance.

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