Skip to main content
Glama
narou-match-mcp

narou-match-mcp

by yukkie3276

小説を読もう!を検索

search_narou

Converts natural-language novel preferences into search terms and filters to find Narou works via public API. Returns title, author, summary, rating, status, and URL metadata without story text.

Instructions

小説を読もう!の作品を、利用者の希望を検索語と条件に変換して探します。Narou Matchの公開検索APIが返す作品情報だけを使い、本文は取得しません。結果にはタイトル、作者、あらすじ、キーワード、評価、完結状態、公式URLなどを含みます。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_narou"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo並び順。relevance
tagsNoなろう公式キーワード。最大10件。
genreNo小ジャンルコード。例: ハイファンタジー201。
limitNo返す作品数。負荷を抑えるため最大20件。
queryNo作品名・あらすじ・キーワードに含まれそうな検索語。自然文から意味のある要素だけを入れる。空文字なら条件検索。
genresNo小ジャンルコードの配列。
is_r15NoR15作品を含めるか。falseならR15を除外。
offsetNo検索結果の開始位置。大量取得には使わない。
statusNo作品の状態。shortは短編作品。all
biggenreNo大ジャンルコード。恋愛1、ファンタジー2、文芸3、SF4など。
has_bookNo書籍化が確認された作品だけに絞るか。
has_animeNoアニメ化が確認された作品だけに絞るか。
has_mangaNo漫画化が確認された作品だけに絞るか。
length_bucketNo作品の文字数。tanpenは掌編、shortは短編。all
include_stalledNo更新が長期間止まった未完作品を候補に残すか。
include_unratedNo評価者がいない作品を含めるか。
min_rating_countNo最低評価者数。未指定ならNarou Matchの既定値。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses the public search API data source, the no-body-text limitation, and the fields returned, but it does not explicitly state read-only behavior, rate limits, error handling, authentication needs, or pagination constraints beyond what the schema already says.

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 tight sentences are front-loaded with the purpose, then the data source and no-body limitation, then the result contents. Every sentence adds useful information and there is 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?

For a 17-parameter search tool with no output schema and no annotations, the description covers the data source, scope, result fields, and the no-body-text limitation. Remaining details live in the fully described schema, though it could say more about read-only behavior or pagination.

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 all 17 parameters are already documented in the input schema. The description adds only generic framing about search terms and conditions plus result fields, without parameter-specific meaning beyond the schema, so the baseline score applies.

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 description uses a specific verb and resource: searching works on 小説を読もう!. It also frames the tool's role as translating a user's wishes into search terms and conditions, which makes the purpose unambiguous.

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?

It gives clear usage context by explaining that user intent should be converted into search terms and conditions, and it sets an important boundary that only public search API metadata is used and body text is not fetched. It does not name alternatives, but no sibling tools are present.

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

Deploy Server

Other Tools