SiteCheck Web Intel

MangaDex manga search by title: id, title, year

search_mangadex_manga

Read-only

MangaDex manga search by title (public API, no key): id, title, year, publication status, content rating, genre tags, last chapter and page link. Metadata only; no chapter pages. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "search_mangadex_manga"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many manga, 1 to 20 (default 5)
`title`	Yes	Title words (1 to 100 characters)

Output Schema

Name	Required	Description	Default
`count`	No
`items`	No
`title`	No
`total`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses that the API is public and keyless and, importantly, that each successful call costs $0.002 USDC via x402 with failures uncharged — a material behavior an agent must weigh before calling. It stops short of describing rate limits, result ordering, or pagination behavior, so it is not fully exhaustive.

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?

The core capability is front-loaded in the first sentence, followed by two short scope/cost clauses; there is no filler. The field enumeration is somewhat long, but each item conveys what the caller receives.

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?

An output schema exists, so return values need not be explained, and the description covers source, scope exclusion, authentication model, and cost — the essentials for a paid, read-only lookup. Missing only minor operational detail such as pagination or result ordering, which is not blocking for a two-parameter search.

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 coverage is 100% with only two parameters, so the schema already documents `title` (1–100 characters) and `limit` (1–20, default 5). The description adds nothing about matching semantics — e.g., substring vs exact matching, or how multi-word titles are handled — so it sits at the baseline.

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 ('MangaDex manga search by title') and enumerates the returned fields (id, title, year, publication status, content rating, genre tags, last chapter, page link). It names the upstream source explicitly, which separates it from the many other `search_*` content-source siblings in the catalog.

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?

Usage is implied by the name and the 'metadata only; no chapter pages' scope limit, which tells the agent when this tool will not help. However, there is no explicit when-to-use guidance, no named alternative for full chapter content, and no note on whether other search tools should be preferred for non-manga queries.

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

All SiteCheck Web Intel 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?