Skip to main content
Glama
zbkm

mmnt-mcp-server

by zbkm

mmnt_cache

Extract cached web pages from the Mamont search engine by providing a unique cache ID, with options for text-only or HTML output.

Instructions

Extract page from Mamont cache

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesunique cache id
onlyTextYesShould the result be text only (no html)

Implementation Reference

  • The core handler function that fetches the cached HTML page from mmnt.ru, decodes from windows-1251 to UTF-8, and extracts plain text from the <pre> element if onlyText is true.
    export async function extractCache(id: string, onlyText: boolean = true): Promise<string> {
        const response = await fetch(`https://www.mmnt.ru/cache2/${id}.html`);
        const buffer = await response.arrayBuffer();
        const html = iconv.decode(Buffer.from(buffer), "windows-1251"); // convert win1251 -> utf8
    
        if (!onlyText) {
            return html;
        }
    
        const $ = cheerio.load(html);
        return $("pre").first().text();
    }
  • src/index.ts:27-37 (registration)
    Registers the 'mmnt_cache' tool with the MCP server, using CacheParams schema and wrapping the extractCache handler.
    server.tool(
        "mmnt_cache",
        "Extract page from Mamont cache",
        CacheParams,
        async ({id, onlyText}) => ({
            content: [{
                type: "text",
                text: JSON.stringify(await extractCache(id, onlyText))
            }]
        })
    );
  • Zod schema defining input parameters for the mmnt_cache tool: id (string) and onlyText (boolean).
    export const CacheParams = {
        id: z.string({description: "unique cache id"}),
        onlyText: z.boolean({description: "Should the result be text only (no html)"})
    };
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'extract' implies a read operation, it doesn't specify whether this requires authentication, has rate limits, affects cache state, or what format the extracted page returns. The description adds minimal behavioral context beyond the basic action.

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 extremely concise at just 5 words with zero waste. It's front-loaded with the core action and resource. Every word earns its place in this minimal description.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the extracted page contains, what format it returns, or how it differs from the search tool. The minimal description leaves too many questions unanswered for proper tool selection and invocation.

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%, so the schema already documents both parameters thoroughly. The description doesn't add any additional meaning about parameters beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose3/5

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

The description 'Extract page from Mamont cache' clearly states the action (extract) and resource (page from Mamont cache), but it's somewhat vague about what exactly 'Mamont cache' refers to and doesn't differentiate from its sibling tool 'mmnt_search'. It provides basic purpose but lacks specificity about the nature of the cache or extraction process.

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?

No guidance is provided about when to use this tool versus its sibling 'mmnt_search'. The description doesn't mention prerequisites, alternatives, or context for usage. Users must infer usage from the tool name and parameters alone.

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