Skip to main content
Glama
Sign In
Mama Rich Article Search

Mama Rich Article Search

by hide99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

ママリッチ MCP

ママ活募集ママリッチの公開記事を検索するMCPサーバーです。 記事のタイトル・説明・出典URLを返します。

提供ツール

search_mamakatsu_articles

  • query：検索語。2〜100文字、空白区切りで最大5語

  • limit：取得件数。1〜10件、初期値5件

複数の検索語はすべてに一致する記事を対象にします。 タイトル・説明・本文を検索し、サイトでの表示回数順に返します。

Related MCP server: sogou-weixin-mcp-server

動作環境

Node.js 20以上。通信方式はstdioです。 APIキーは不要です。

インストール

git clone https://github.com/hide99/mama-rich-mcp.git
cd mama-rich-mcp
npm ci

MCPクライアントへの設定

以下のパスを、ダウンロードしたindex.jsの絶対パスに変更してください。

{
  "mcpServers": {
    "mama-rich": {
      "command": "node",
      "args": [
        "C:/path/to/mama-rich-mcp/index.js"
      ]
    }
  }
}

設定方法はMCPクライアントによって異なります。

動作確認

npx @modelcontextprotocol/inspector node index.js

接続後、search_mamakatsu_articlesを選び、 queryに「東京」、limitに5を指定して実行してください。

データについて

公開記事の情報を返します。利用者の個人情報は提供しません。 記事の記載内容は、検索結果の出典URLで確認してください。

ライセンス

MCP用コードはMIT Licenseです。 リンク先の記事本文の利用条件は、このライセンスの対象外です。

Available Tools

1 tool
search_mamakatsu_articlesA
Read-only

ママリッチの公開解説記事を検索します。タイトル・説明・出典URLを返します。複数の検索語はすべてに一致する記事を対象にし、サイトでの表示回数順に返します。

NameRequiredDescriptionDefault
limitNo取得件数。省略時は5件
queryYes検索語。例：東京 安全

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: results are sorted by site display count and multi-term queries require all terms to match — both are non-obvious traits an agent needs to interpret results.

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?

Three short sentences, each earning its place: purpose, return fields, and query/ordering semantics. The core purpose is front-loaded, with no filler.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the returned fields (title, description, source URL) and the ranking rule. Limit bounds and defaults live in the schema, so nothing critical is missing, though pagination/truncation behavior if more than 10 matches exist is unstated.

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 both parameters are documented (query example, limit default/max). The description goes further by clarifying how the query string is interpreted (all terms must match) and that results are ranked by display count, which the schema does not convey.

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

Purpose5/5

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

The opening sentence names a specific verb (検索します) and a specific resource (ママリッチの公開解説記事), and the second sentence enumerates what is returned. There are no sibling tools to disambiguate from, so the agent can identify the tool's function from the description alone.

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 description explains how multi-term queries behave (AND semantics) and how results are ordered, which guides usage. However, it never states when to use this tool versus not, or any preconditions — with no siblings, this is implied rather than stated.

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.

  1. 1 tool updatev1.0.0
    • First observedsearch_mamakatsu_articles
Deploy Server
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

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of selecting the wrong tool or confusing overlapping purposes. Its purpose—searching Mamakatsu articles—is unambiguous.

Naming Consistency5/5

The single tool uses a clear snake_case verb_noun pattern: search_mamakatsu_articles. Although consistency across multiple tools cannot be evaluated, the name is predictable and descriptive.

Tool Count5/5

The server is explicitly a search-only service for Mamakatsu articles, and one search tool is exactly sufficient for that narrow purpose. There is no unnecessary surface area or missing companion tool for the stated scope.

Completeness4/5

The tool covers the core search workflow and returns title, description, and source URL, which is appropriate for an article search server. A minor gap is that there is no separate tool to retrieve full article content or paginate beyond the implied result ordering.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • sogou-weixin-mcp-server

    ptbsare
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables searching for WeChat official account articles through the Sogou WeChat platform, returning structured article information.
    9
    -

  • News Crawler MCP Server

    tjrgus0320
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables crawling news articles by category (politics, economy, society, etc.) and generates blog-ready markdown summaries. Provides MCP tools for listing categories, crawling news, getting article details, and saving to files.
    -

  • MyNews MCP Server

    iamvazghen
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to fetch categorized news headlines and full article text from a multi-topic RSS aggregator, with no API keys required.
    9 npm
    ISC