Nativ

localize_subtitles

Localize subtitles in-memory. Provide an SRT/ITT and/or a video (STT).

    Args:
        target_language_codes: Comma-separated codes (e.g. "fr,de,ja").
        subtitle_path: Optional public HTTPS subtitle URL (hosted) or local path (stdio).
        video_path: Optional public HTTPS video URL (hosted) or local path (stdio) for STT.
        glossary_path: Optional public HTTPS glossary URL (hosted) or local path (stdio).
        source_language_code: Source language code.
        context: Optional localization context.
        formality: Optional formality override.
        output_dir: Local output directory (stdio). Hosted mode always returns subtitle download URLs.

Input Schema

Name	Required	Default
`context`	No
`formality`	No
`output_dir`	No
`video_path`	No
`glossary_path`	No
`subtitle_path`	No
`source_language_code`	No	en
`target_language_codes`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does add real value: it discloses mode-dependent behavior ('Hosted mode always returns subtitle download URLs', output_dir only applies to stdio). It omits cost, rate limits, failure behavior, and whether localization is destructive or repeatable.

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

Conciseness4/5

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

The leading sentence front-loads the core action, and the Args block is scannable with no filler. The raw docstring formatting (indentation, trailing blank line) is slightly untidy but costs nothing in comprehension.

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 an 8-parameter tool with no annotations, the description covers inputs and the hosted/stdio output split, and an output schema exists so return values need no explanation. It still leaves open whether subtitle_path or video_path is mandatory and what happens if neither is supplied.

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?

Schema coverage is 0%, so the description must compensate, and it documents all eight parameters including the hosted-URL vs local-path split per path argument and a concrete example format for target_language_codes. Weak spots remain: 'context' and 'formality' are described only tautologically, with no expected values or format.

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?

States a specific verb and resource ('Localize subtitles in-memory') and clarifies the accepted input types (SRT/ITT file and/or video via STT). The 'in-memory' qualifier implicitly distinguishes it from localize_subtitle_file, but no sibling is named explicitly, so an agent must infer the boundary.

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?

There is no guidance on when to pick this over localize_subtitle_file, translate, translate_dialogue, or upload_subtitle, nor any stated prerequisites. Only a weak implication ('and/or a video (STT)') hints at input-mode selection, leaving the agent to guess.

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

All Nativ tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.