トゥーンエル

作品と話を探す

search_works

Read-onlyIdempotent

トゥーンエルの縦読み漫画の作品と話を、言葉とジャンルで探す。題名・あらすじ・登場人物のほか、作品が扱う仕事・暮らし・制度・お金・手続きの言葉（例：無申告加算税、施工管理、置き配、生活保護）からも探せる。用語の解説（get_glossary）や、その言葉が出てくる話を探す入口にもなる。query が空なら全作品の一覧（id・名前・ジャンル・URL・話の数だけ）を返す。当たった話のうち第2話以降には spoiler の印（up_to_episode を渡すと、それより後の話は返さない）。

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_works"
  }
}

Input Schema

Name	Required	Description
`genre`	No	ジャンルの id か名前（例：isekai／異世界転生、mystery／ミステリー）
`query`	No	探す言葉（例：加算税、施工管理、置き配、配車）。空白で区切ると、全部を含む物を返す
`up_to_episode`	No	利用者が読んだ話の番号（ネタバレを避ける）。これより後の話のあらすじ・用語を省く。分からなければ省く（全部を返し、第2話以降に spoiler の印）

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive context beyond them: the empty-query return shape (id, name, genre, URL, episode count only) and spoiler semantics (episode 2+ flagged, up_to_episode suppresses later episodes). This is exactly the kind of behavior an agent cannot infer from the annotations.

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?

Front-loaded with purpose and searchable fields, then return/spoiler behavior. The parenthetical example terms are dense but earn their place as concrete cues; overall it is a tightly packed but purposeful paragraph.

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 carries the return-shape burden and does so partially (empty-query fields, spoiler flags), which is adequate for a read-only search tool. It does not detail the non-empty query result shape beyond spoiler marks, leaving a small gap.

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 the baseline is 3; the description goes slightly beyond by explaining that an empty query yields a full works list, which the schema's query description does not state. The spoiler/up_to_episode relationship is also reinforced in prose.

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 states a specific verb and resource ('トゥーンエルの縦読み漫画の作品と話を…探す') and enumerates the searchable fields (title, synopsis, characters, and domain terms like tax/construction/life-welfare). It also distinguishes itself from the sibling get_glossary as a complementary entry point, so an agent can tell them apart without opening schemas.

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 conditional guidance: an empty query returns a full list, and it points to get_glossary for term definitions. It doesn't state explicit exclusions (e.g. when to prefer list_episodes or list_new_episodes), which keeps it from a 5.

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

All トゥーンエル tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?