Aleksei Shipulin — CV, projects and writing

Read a complete source

read_content

Read-onlyIdempotent

Read one published entry as copyable Markdown with its dates, contribution, translation status and source links. Use the returned source text for factual claims.

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": {
      "id": "<id>"
    },
    "name": "read_content"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Exact item id or translation key returned by search_content or overview.
`lang`	No	Language of the returned edition; defaults to English.	en

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation with no open-world access. The description adds useful behavioral detail beyond that by specifying the return format, metadata fields, translation status, source links, and the intended use of the returned text for factual claims; it does not cover error cases or missing-translation behavior.

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?

The description is two tight sentences with no redundant wording. It front-loads the core action and return format before adding the factual-claims guidance.

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?

There is no output schema, so the description carries the burden of explaining the return value, and it does so by naming the Markdown format, dates, contribution, translation status, and source links. Combined with the fully described parameters and safe-read annotations, this is complete enough for an agent to invoke the tool correctly.

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%, and the schema already explains that id is an exact item id or translation key from search_content or overview, and that lang selects the returned edition. The description does not add meaning beyond those parameter definitions, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: reading one published entry, with a clear scope of returning Markdown plus metadata and source links. It implicitly contrasts with broader search/overview tools by focusing on a single entry, but it does not explicitly name or differentiate against any sibling.

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

Usage Guidelines3/5

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

The instruction to use the returned source text for factual claims gives some usage context. However, it does not say when to choose this tool over search_content, overview, related_content, or get_profile, nor does it state exclusions or prerequisites in the description itself.

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

All Aleksei Shipulin — CV, projects and writing tools Inspect

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

Need Help?