Skip to main content
Glama
RichardGuan1

EH Index MCP

by RichardGuan1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List gallery torrents

eh_get_torrents
Read-onlyIdempotent

Retrieve current and outdated torrent metadata and official .torrent links for E-Hentai and ExHentai galleries without downloading files. Provide a gallery URL or ID/token to get torrent details.

Instructions

Read current and outdated torrent metadata and official .torrent links. This tool never downloads a torrent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoTarget site; gallery URLs override this when a URL is providede-hentai
galleryNoGallery ID and token; provide this or galleryUrl, but not both
galleryUrlNoFull gallery URL; provide this or gallery, but not both

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
torrentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / gallery / description
      Added value: +"Gallery ID and token; provide this or galleryUrl, but not both"
    • addedInput schema / properties / galleryUrl / description
      Added value: +"Full gallery URL; provide this or gallery, but not both"
    • addedInput schema / properties / site / description
      Added value: +"Target site; gallery URLs override this when a URL is provided"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already signal read-only and non-destructive behavior. The description goes beyond them by explicitly stating 'This tool never downloads a torrent,' which is a meaningful behavioral guarantee not fully implied by readOnlyHint. It also clarifies that it returns metadata and official .torrent links rather than torrent file contents.

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?

The description is two short sentences with no filler. It front-loads the core purpose and then supplies the most important behavioral caveat in the second sentence. Every part earns its place.

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

Completeness5/5

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

Given the strong annotations, fully self-describing input schema, and presence of an output schema, the description covers everything an agent needs to choose and invoke the tool correctly. It clarifies scope, behavior, and the key non-download guarantee without unnecessary detail.

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 the parameters are already fully documented with types, defaults, formats, and mutual exclusivity. The description adds no additional parameter-level meaning, so it stays at the baseline rather than earning extra credit.

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 ('Read') and names a clear resource ('torrent metadata and official .torrent links'). It also adds a distinguishing detail by covering both current and outdated torrent metadata, which separates it from gallery metadata or search tools in the sibling list.

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?

The description makes clear the tool is for reading torrent metadata and links rather than downloading them, which establishes a useful boundary. It does not explicitly name alternative sibling tools or state when not to use it, but the torrent-specific focus provides clear context.

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