Skip to main content
Glama

find_subtitles

Search OpenSubtitles for subtitle candidates without downloading, so users can choose one or verify an exact-file hash match before spending a download.

Instructions

Search OpenSubtitles and return the candidates without downloading anything. Use this when the user should choose, or to check what exists before spending a download. Each result carries a file_id for download_subtitle, plus moviehash_match — true means it is synced to this exact file. Costs no download quota. Requires the user's own OpenSubtitles API key in the opensubtitles_api_key setting.

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

Input Schema

NameRequiredDescriptionDefault
fileNoVideo to match against. Defaults to the playing file.
hashNoMatch by file hash as well as title (default true). Set false to search by title only.
queryNoSearch text. Omit to derive a title from the playing file's name.
languagesNoComma-separated OpenSubtitles language codes, e.g. "zh-CN,en"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses that no download quota is consumed, that the user's own API key must exist in a named setting, and that moviehash_match indicates sync to this exact file. It stops short of rate limits, result-count caps, or what happens on auth failure, which are the remaining behavioral gaps for a no-annotation tool.

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?

Front-loads the core action, then layers usage, return-value meaning, quota cost, and auth prerequisite in short clauses with no filler. Every sentence supplies a distinct fact an agent would otherwise have to guess.

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?

With no output schema, the description must say what comes back, and it names two key return fields (file_id, moviehash_match) plus the quota implication. It is complete enough to call correctly, though a fuller picture of the result set (count, ranking, error cases) is absent.

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 coverage is 100%, so file, hash, query, and languages are already documented in the schema; the description adds only indirect meaning by explaining what a hash match proves. It does not elaborate on query derivation or language code handling beyond the schema, so the baseline 3 applies.

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 verb and resource ("Search OpenSubtitles and return the candidates without downloading anything") and explicitly scopes out the download action, which distinguishes it from download_subtitle. An agent can tell from the first sentence that this is a discovery step, not a fetch step.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions: "when the user should choose" and "to check what exists before spending a download," and names download_subtitle as the follow-on alternative for the file_id. The relationship between search and download is completely clear from the text alone.

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