Skip to main content
Glama
Sign In
M-Team MCP Server

M-Team MCP Server

by 07freedom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_torrent_detail

Get full details of a torrent by its ID, including name, size, description, ratings, file count, and seeder/leecher counts.

Instructions

Get detailed information for a specific torrent by its ID.

Args: torrent_id: The numeric torrent ID (e.g. "1125330").

Returns: A formatted string with full torrent details including name, size, description, ratings, file count, seeder/leecher counts, etc.

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": {
      "torrent_id": "<torrent_id>"
    },
    "name": "get_torrent_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
torrent_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Removedv0.1.0
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations, so description carries burden. Lists return fields (name, size, etc.) indicating read-only behavior, but doesn't disclose error handling, permissions, or rate limits. Adequate but not rich.

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?

Concise, front-loaded purpose, clear Args/Returns structure. Every sentence adds value.

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?

Complete for a simple one-param read tool with no annotations: covers purpose, parameter, return. Lacks error info but acceptable for given complexity.

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

Parameters5/5

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

Schema coverage is 0%, but description adds full meaning: param is numeric ID, with example and explanation. Alone it fully documents the parameter.

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?

Clearly states it retrieves detailed info for a specific torrent by ID, with a specific verb and resource. Distinguishes from siblings (search_torrents, download_torrent) by focusing on detail retrieval.

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?

Implies use when you have a torrent ID via 'by its ID' and example, but no explicit when-not or alternatives. Context is clear but lacks exclusions.

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