EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Search by local image file

eh_search_by_file

Read-onlyIdempotent

Find exact image matches on E-Hentai or ExHentai by locally hashing a chosen file's SHA-1. The file stays on your device; only the hash is used for search.

Instructions

Read one explicitly provided absolute local file, calculate SHA-1 locally, and perform exact image search. The file is never uploaded.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to one user-selected regular file; directories and wildcards are rejected
`site`	No	Target site; gallery URLs override this when a URL is provided	e-hentai

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Oct 2, 2026

addedOutput schema / properties / result / properties / result / properties / galleries / items / properties / site
```
Added value: +{
+  "enum": [
+    "e-hentai",
+    "exhentai"
+  ],
+  "type": "string"
+}
```

changedOutput schema / properties / result / properties / result / properties / galleries / items / required

Previous value: -[
-  "gid",
-  "token",
-  "url",
-  "title",
-  "category",
-  "uploader",
-  "posted",
-  "pages",
-  "rating",
-  "tags",
-  "thumbnailUrl"
-]New value: +[
+  "gid",
+  "token",
+  "site",
+  "url",
+  "title",
+  "category",
+  "uploader",
+  "posted",
+  "pages",
+  "rating",
+  "tags",
+  "thumbnailUrl"
+]

Changed1 schema field changedv0.1.2Aug 26, 2026
- addedInput schema / properties / site / description
```
Added value: +"Target site; gallery URLs override this when a URL is provided"
```
First observedv0.1.0Aug 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds genuinely new facts beyond those: hashing happens locally and the file is never uploaded, which is the key privacy/behavioral trait for this tool. It stops short of describing search-result behavior or failure modes.

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?

Two tight sentences with zero filler; the local-processing and no-upload facts are front-loaded where an agent will see them.

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?

An output schema exists, annotations cover the safety profile, and the one behavior an agent could not infer from structured fields (no upload, local hashing) is stated. Nothing essential for correct invocation is missing.

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 both parameters (path, site) are already documented in the schema, including the absolute-path requirement and enum values. The description only echoes the absolute-file notion and says nothing about the site parameter, so baseline 3 is right.

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?

States a specific sequence of actions (read file, compute SHA-1, exact image search) on a specific resource, which cleanly separates it from eh_search_by_hash (takes a hash, not a file) and eh_find_similar_galleries (visual similarity, not exact). An agent can pick the right tool without opening a schema.

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?

"One explicitly provided absolute local file" implies when the tool applies, and the schema's constraints reinforce it. But there is no explicit when-not guidance and no routing to eh_search_by_hash or eh_find_similar_galleries for the adjacent cases an agent is likely to face.

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