Skip to main content
Glama
Sign In
torrent-mcp

torrent-mcp

by luisriverag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_indexers

Retrieve available Jackett indexers for torrent searches. Filter to configured-only to show active indexers ready for use in your pipeline.

Instructions

List Jackett indexers known to the server.

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": "list_indexers"
  }
}

Input Schema

NameRequiredDescriptionDefault
configured_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden of indicating behavior, and 'List' makes the read-only nature apparent. However, it does not disclose that the default configured_only=true limits the result to configured indexers, which is material to interpreting the returned data.

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 one short, front-loaded sentence with no filler words. Every word contributes to identifying the tool's action and object.

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

Completeness3/5

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

For a simple read-only list with one optional boolean and an output schema, the description is close to sufficient. It is incomplete because it does not clarify the effect of the configured_only parameter or reconcile 'known to the server' with the default configured-only behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not mention configured_only or explain that it filters the listed indexers. The schema's title and default provide some meaning, but the description adds nothing beyond the tool's overall subject.

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 uses a specific verb and resource: 'List Jackett indexers known to the server.' It clearly identifies the tool as a listing operation for indexers and is not a tautology. It does not explicitly differentiate from sibling listing tools such as list_profiles, but the resource is sufficiently distinct.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool instead of a sibling such as switch_indexer or search_torrents, and it never mentions the configured_only parameter or when to toggle it. Usage context is entirely absent.

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