Skip to main content
Glama
zbkm

mmnt-mcp-server

by zbkm

mmnt_search

Perform a search on the Mamont search engine by providing a query and page number to retrieve results.

Instructions

Search in Mamont search engine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesquery string
pageYespage number

Implementation Reference

  • The core search function `searchMamont` that fetches results from Mamont search engine, parses HTML with cheerio, and returns structured search results. This is the handler for the 'mmnt_search' tool.
    export async function searchMamont(request: string, page: number = 0): Promise<SearchResult> {
        const ot = page * 10 + 1;
        const response = await fetch(`https://www.mmnt.ru/get?st=${encodeURIComponent(request)}&in=w&ot=${ot}`);
    
        const buffer = await response.arrayBuffer();
        const text = iconv.decode(Buffer.from(buffer), "windows-1251"); // convert win1251 -> utf8
        const $ = cheerio.load(text);
    
        const result: SearchResult = [];
        $(".link_block").each((i, elem) => {
            if (i == 0) return;
    
            const linkElement = $(elem).find("p.link_p a").first();
            const title = linkElement.text().trim();
            const description = $(elem).find("p.desc_p").text().trim();
            const url = $(elem).find("p.link_p a").first().attr("href")!;
            const cache = $(elem).find("p.cache_p a").first().attr("href")?.match(/\/cache\/([a-f0-9]+)\.html/)?.[1];
            const web_archive = $(elem).find("p.arch_p a").first()?.attr("href");
    
            result.push({
                title,
                description,
                url,
                ...(cache ? {cache} : {}),
                ...(web_archive ? {web_archive} : {}),
            });
        });
    
        return result;
    }
  • Zod schema for the 'mmnt_search' tool parameters: `query` (string) and `page` (number).
    export const SearchParams = {
        query: z.string({description: "query string"}),
        page: z.number({description: "page number"})
    };
  • src/index.ts:15-25 (registration)
    Registration of the 'mmnt_search' tool on the McpServer. It defines the tool name, description, input schema (SearchParams), and the handler lambda that calls searchMamont.
    server.tool(
        "mmnt_search",
        "Search in Mamont search engine",
        SearchParams,
        async ({query, page}) => ({
            content: [{
                type: "text",
                text: JSON.stringify(await searchMamont(query, page))
            }]
        })
    );
  • Type definitions for the search result (SearchResultElement and SearchResult) returned by the handler.
    export type SearchResultElement = {
        title: string
        description: string
        url: string,
        cache?: string,
        web_archive?: string
    }
    
    export type SearchResult = SearchResultElement[]
Behavior1/5

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

No annotations are provided, so the description alone must disclose behavioral traits. It only says 'Search in Mamont search engine' without indicating whether the operation is read-only, any side effects, authentication needs, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks depth. It could include more context without being verbose, so it is adequate but not exemplary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description should provide complete guidance on the tool's behavior and return values. It fails to explain what the search returns, pagination details, or any constraints.

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?

Input schema coverage is 100% with descriptions for both parameters. The description adds no extra meaning beyond the schema, so baseline 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 clearly states the tool performs a search in the Mamont search engine, which is a specific verb-resource combination. Although it does not explicitly differentiate from the sibling mmnt_cache, the distinct resource and action imply differentiation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool vs. alternatives, such as mmnt_cache. There is no mention of context, prerequisites, or scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zbkm/mmnt-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server