Skip to main content
Glama
philogicae

Torrent Search MCP Server

by philogicae
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Torrents

search_torrents

Find and rank torrents from multiple providers based on quality, health, and size to recommend the top 3-5 results with clear reasons for each choice.

Instructions

Perform an advanced torrent search across multiple providers.

Result Analysis & Ranking:

  1. Quality: Prefer 1080p or 4k, over 720p.

  2. Efficiency: Prefer h265/HEVC for better quality/size ratio.

  3. Health: Maximize seeders + leechers.

  4. Size: Prefer smaller files within the same quality bracket.

  5. Language: Ultimately, if multiple equivalent options are available, choose the one with more languages.

Response Requirements:

  • Recommend the top 3-5 results maximum.

  • For each recommendation, include: Filename, Size, Seeds/Leechs, Date, Source, and a 1-sentence "Why this?" reason.

  • If results are poor, irrelevant or too diverse, suggest specific keywords to improve the search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesOptimized search keywords, lowercase and space-separated. Strip generic terms (movie, torrent, download), filler words (the, a, of) and technical tags (1080p, h265, bluray) unless explicitly requested. TV shows: 'name sXXeYY' for episodes, 'name sXX' for seasons. Add 'multi' only if a multi-language version is requested.
user_intentYesUser's overall intention (e.g. 'latest episode of Sample Show').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.5.0
    • changedInput schema / properties / user_intent / description
      Previous value: -"User's overall intention (e.g. 'latest episode of Breaking Bad')."New value: +"User's overall intention (e.g. 'latest episode of Sample Show')."
  2. Changed2 schema fields changedv4.3.3
    • addedInput schema / properties / query / description
      Added value: +"Optimized search keywords, lowercase and space-separated. Strip generic terms (movie, torrent, download), filler words (the, a, of) and technical tags (1080p, h265, bluray) unless explicitly requested. TV shows: 'name sXXeYY' for episodes, 'name sXX' for seasons. Add 'multi' only if a multi-language version is requested."
    • addedInput schema / properties / user_intent / description
      Added value: +"User's overall intention (e.g. 'latest episode of Breaking Bad')."
  3. Changed7 schema fields changedv2.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / max_items
      Removed value: -{
-  "default": 10,
-  "title": "Max Items",
-  "type": "integer"
-}
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / sources
      Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Sources"
-}
    • addedInput schema / properties / user_intent
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "query"
-]New value: +[
+  "user_intent",
+  "query"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  4. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently explains the ranking criteria (quality, efficiency, health, size, language) and the response format (top 3-5 results with specific fields and 'Why this?' reasons), plus the fallback of suggesting keywords. This is substantial and goes beyond basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with headers and bullet points, making it scannable, but it's fairly long with detailed ranking and response requirements. While each section is informative, it could be more concise; the ranking criteria and response format are somewhat verbose, though they do add context. It's not overly redundant but is longer than strictly necessary.

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?

Given the complexity of the tool (multi-provider search, ranking, response formatting) and the presence of an output schema, the description covers the essential behavior, query construction, ranking logic, and response requirements, including a fallback for poor results. It doesn't mention auth or limitations, but for a search tool with an output schema, it's sufficiently complete for correct invocation.

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?

The schema already describes both parameters with 100% coverage, so the baseline is 3. The description adds significant value by detailing how to construct the query (strip generic terms, TV show format, 'multi' flag), which is not in the schema. This enriches the meaning of the query parameter beyond its type/description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs an advanced torrent search across multiple providers, which is a specific action and resource. However, it doesn't explicitly differentiate itself from siblings like popular_torrents or get_torrent beyond calling itself 'advanced' and mentioning 'multiple providers', so it's clear but not fully distinguishing.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It gives detailed ranking and response instructions, but doesn't say when to prefer this over popular_torrents or other siblings, nor does it mention exclusions or conditions. Usage is only implied by the search nature.

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