Skip to main content
Glama

Semerenko Group Public Site MCP

Search Semerenko public content

sem.search_content
Read-only

Keyword search (not semantic) over public posts, pages, listings, and market insights. Returns the best-matching pages with canonical URL, title, excerpt, and categories. Use it to find existing pages to cite or link to before writing new content. For a "is this topic already covered / what should I link to" judgement use sem.find_related; to browse the whole catalogue use sem.list_content.

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": {
      "query": "<query>"
    },
    "name": "sem.search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional content-type filter. Default "any".
limitNoMaximum results to return. Default 10.
queryYesKeywords to match against title and content.

Output Schema

NameRequiredDescriptionDefault
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds genuinely non-obvious behavior beyond that: matching is keyword-based rather than semantic, and results are ranked "best-matching" with a specific field set. It stops short of describing ranking factors or truncation behavior, which keeps it at a 4 rather than a 5.

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 front-loaded sentences: what it does, what it returns, then routing. The search-mode caveat sits in the first clause, where an agent skimming will catch it, and no sentence is redundant with another.

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?

An output schema exists, annotations cover the read-only profile, and all three parameters are documented in the schema. Given that support, the description covers the only remaining ambiguities — search mode, result fields, and sibling routing — so nothing material is missing for a correct invocation.

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 and the schema already documents all three parameters and the enum. The description still adds real meaning about how `query` is interpreted — literal keyword matching, explicitly not semantic — which is the single most consequential thing to know when composing a query.

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 gives a specific verb and resource ("Keyword search ... over public posts, pages, listings, and market insights") and immediately disambiguates the search mode ("not semantic"). It also enumerates the returned fields, so an agent can tell it apart from sem.find_related and sem.list_content without opening any schema.

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

Usage Guidelines5/5

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

It states the concrete task it serves ("find existing pages to cite or link to before writing new content") and names two alternatives with the exact condition that selects each: sem.find_related for the coverage/linking judgement, sem.list_content for browsing the catalogue. When-to-use and when-to-use-something-else are both explicit.

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