Skip to main content
Glama

Semerenko Group Public Site MCP

Read public Semerenko URL

sem.read_public_url
Read-only

Fetch the clean public title, metadata, categories, and full plain-text body (up to ~20k chars) for one published Semerenko Group URL. Use after search/find_related to read a candidate page in full. Returns an error if the URL is not a published public page.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute Semerenko Group URL to read.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
textNo
typeNo
titleNo
excerptNo
readApiNo
modifiedNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 safety is covered. The description adds genuinely new behavior beyond that: the body is truncated at ~20k chars, and the call fails (returns an error) when the URL is not a published public page. That pre-empts the two most likely failure modes an agent would hit.

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 resource and returned fields, then usage sequencing, then the failure condition. No filler and no restatement of the tool name or title.

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, so return values need not be fully specified, yet the description still names the returned fields and the body size cap. Combined with the stated error case and the single fully-described parameter, an agent has everything needed to call this correctly on the first attempt.

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?

With a single required parameter at 100% schema coverage, the schema already documents format=uri and that the value must be an absolute Semerenko Group URL. The description reinforces the 'published public' constraint but adds no syntax, normalization, or encoding detail beyond the schema, 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 ('Fetch') and resource ('one published Semerenko Group URL') and enumerates exactly what comes back: title, metadata, categories, and full plain-text body. The scope word 'one' and the 'full plain-text body' phrasing clearly separate it from the search/list siblings that return candidates rather than page contents.

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?

Gives clear sequencing guidance — 'Use after search/find_related to read a candidate page in full' — which tells the agent this is a second-step drill-down tool, and names two concrete alternatives by name. It also implies a boundary via the error condition for non-published URLs, though it never explicitly states when another tool (e.g. get_property) would be preferred.

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