Skip to main content
Glama
enesjakozh
zbkm

mmnt-mcp-server

by zbkm
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

mmnt-mcp-server

MCP server for the Mamont search engine.

Tools:

  • mmnt_search

    • search query on search engine

    • inputs

      • query - query string

      • page - page number

  • mmnt_cache

    • retrieve page from search page cache

    • inputs

      • id - unique cache id

      • onlyText - should the result be text only (no html)

Install

{
  "mcpServers": {
    "mmnt": {
      "command": "npx",
      "args": ["-y", "mmnt-mcp-server"]
    }
  }
}

Available Tools

2 tools
mmnt_cacheC

Extract page from Mamont cache

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

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description is too brief to convey behavioral traits such as error handling, idempotency, or side effects. The agent gains little insight beyond the name.

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?

One short sentence, no fluff. Could be slightly expanded with key details without losing conciseness.

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?

Despite simple parameters, the tool lacks context on return value, error conditions, or how 'onlyText' affects output. Incomplete for an agent to use reliably.

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?

The input schema already fully describes the two parameters with descriptions. The tool description adds no extra meaning beyond the schema, so baseline score applies.

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 action 'extract page' and the resource 'Mamont cache'. However, it does not differentiate from the sibling tool 'mmnt_search', which likely serves a different purpose.

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 on when to use this tool versus the alternative 'mmnt_search'. No context on prerequisites or typical use cases.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updates
    • First observedmmnt_cache
    • First observedmmnt_search
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one extracts pages from a cache, while the other searches in a search engine. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.

Naming Consistency5/5

Both tools follow a consistent 'mmnt_' prefix pattern with descriptive suffixes ('cache' and 'search'), indicating they belong to the same server and domain. The naming is uniform and predictable.

Tool Count2/5

With only two tools, the server feels thin for a general-purpose Mamont-related service. While it covers cache extraction and search, typical domains like this might benefit from additional tools for operations such as updating cache or advanced search filters.

Completeness2/5

The tool surface is severely incomplete for a Mamont domain, as it only provides extraction and search without any update, deletion, or management capabilities. This creates dead ends for agents needing to modify or interact more fully with the system.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

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