Skip to main content
Glama

OpenSubtitles

Account and quota

get_user_info
Read-onlyIdempotent

The logged-in OpenSubtitles user's level, VIP status, daily download allowance and downloads remaining, so you can plan downloads. Needs a configured login; does not use quota.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
vipYes
levelYes
user_idYes
downloads_countYes
allowed_downloadsYes
remaining_downloadsYes
allowed_translationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needs to add context, and it does: a configured login is required, and the call 'does not use quota' - a meaningful side-effect clarification an agent could not get from annotations. It does not describe error behavior when login is missing.

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?

A single sentence that leads with what is returned, then the planning rationale and the login constraint. Nothing in it is redundant.

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 parameters and an output schema already defining the response shape, the description only needs auth and quota behavior, which it supplies. Only the failure mode for an unconfigured login is left implicit.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; per the zero-parameter baseline this earns a 4.

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?

The description names the exact resource (the logged-in OpenSubtitles user's account) and enumerates the specific fields returned: level, VIP status, daily allowance, downloads remaining. That is clearly distinct from sibling tools like search_subtitles or download_subtitle, so an agent can identify the tool without opening its schema.

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

Usage Guidelines4/5

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

It states the purpose-driven context for calling it ('so you can plan downloads') and a precondition ('Needs a configured login'), which is useful routing and gating information. It stops short of explicitly naming alternatives or when-not-to-use cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.