Skip to main content
Glama

Конкорданс

kwic
Read-onlyIdempotent

Find all occurrences of a Russian word or phrase with surrounding context, optionally by lemma, to inspect usage and quote accurately.

Instructions

Найти все вхождения слова или словосочетания в тексте с контекстом (конкорданс KWIC).

Используйте, чтобы увидеть, как слово употребляется в тексте, и цитировать точно. Слова сравниваются без учета регистра и буквы ё, с by_lemma - по леммам ruMorph в контексте предложения (слово запроса - по любой лемме своих разборов); словосочетание не переходит через конец предложения.

В результате "n_matches" - число вхождений, "matches" - строки по порядку в тексте: контекст слева "left", вхождение "keyword", как оно записано в тексте, и контекст справа "right". Строки ограничены параметром limit и общим объемом ответа около 40 тысяч символов. Ключ "warnings" - предупреждения: текст не на русском языке, показаны не все вхождения.

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": {
      "keyword": "<keyword>"
    },
    "name": "kwic"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoАбсолютный путь к текстовому файлу в UTF-8 на машине, где запущен сервер, вместо text: длинный текст не нужно пересылать в аргументе
textNoТекст на русском языке; вместо него можно задать path
limitNoНаибольшее число строк ответа
windowNoЧисло слов контекста слева и справа
keywordYesСлово или словосочетание
by_lemmaNoИскать все формы слова по лемме: «кот» находит «кота», «коты»

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, yet the description adds real behavioral detail: matching is case- and ё-insensitive, by_lemma uses ruMorph lemmas in sentence context, phrases never cross a sentence boundary, results are truncated by limit and an overall ~40k character cap, and a warnings key flags non-Russian text or partial results. The only shortfall is that part of this text restates return fields already exposed by the output schema.

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?

Purpose is front-loaded in the first sentence, followed by matching semantics and then result shape; every sentence carries information. The enumeration of output keys (n_matches, matches, left, keyword, right) duplicates what the output schema already declares and is the one place where wording does not fully earn its space.

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?

For a 6-parameter read-only tool with full schema coverage, annotations, and an output schema, the description covers everything an agent needs: what it returns, how matching normalizes case and ё, how lemma search behaves, truncation behavior, and the warnings channel. No material gap remains.

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, but the description genuinely adds meaning beyond the schema: by_lemma is explained as ruMorph lemma lookup within sentence context with the query word matching any of its parses, and the sentence-boundary restriction on phrases is stated. It also notes that limit truncates result rows, tying the parameter to the visible 40k character response cap.

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?

States a specific verb and resource: find all occurrences of a word or phrase with context, explicitly labeled as a KWIC concordance. An agent can immediately tell this is a per-occurrence context listing rather than an aggregate statistic. It does not name or contrast with siblings such as collocations or dispersion, so it stops short of a 5.

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 a clear when-to-use rationale: to see how a word is used in the text and to quote it precisely. There are no explicit exclusions or named alternatives (e.g., when to prefer collocations or dispersion instead), which keeps it below a 5, but the usage context is stated rather than merely implied.

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