Skip to main content
Glama
ibeal
by ibeal

tidal_login

Authenticate with TIDAL via OAuth device flow: initiate login, share the verification URL for user approval, then call again to complete the session.

Instructions

Authenticate with TIDAL via OAuth device flow. This tool is non-blocking and
stateful — you may need to call it more than once to complete login.

Possible responses:
  - {"status": "success", "user_id": ...}
      The user is authenticated. No further action needed.
  - {"status": "pending", "verification_url": "...", "expires_in": <seconds>}
      A login is in progress. SHOW the verification_url to the user verbatim
      and ask them to open it in their browser and approve the login. After
      they confirm, CALL THIS TOOL AGAIN to finalize the session. You may
      need to poll a few times (wait a few seconds between calls). The same
      verification_url is returned on every pending poll until it expires.
  - {"status": "error", "message": "..."}
      Something failed; relay the message to the user.

Returns:
    A dictionary with the authentication status as described above.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so excellently. It discloses that the tool is non-blocking and stateful, enumerates all possible response statuses, explains what each means, and tells the agent what to do for each. No behavioral surprises are left hidden.

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 well-structured with clear response cases and front-loaded with the core purpose and key behavioral caveat. Every sentence adds useful information, and the formatting makes the states easy for an agent to parse.

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

Completeness5/5

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

This is a stateful, multi-call authentication flow with no output schema, so the description must be thorough to compensate. It fully covers the pending, success, and error cases, the user interaction requirement, polling behavior, and URL stability. Nothing essential is missing.

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 has zero parameters, so the baseline of 4 applies. There are no parameter semantics to document, and the description appropriately focuses on behavior and return values instead.

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 clearly states the tool authenticates with TIDAL via OAuth device flow, which is a specific action and resource. It is clearly distinct from all sibling tools, which are music/playlist operations rather than authentication.

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?

The description gives explicit step-by-step usage guidance: show the verification_url verbatim, ask the user to approve, then call the tool again. It also explains that polling may be needed and that the same URL is returned until expiration. This is unusually actionable guidance.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ibeal/tidal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server