Cinve

Estado de autenticación

get_auth_status

Read-onlyIdempotent

Check Cinex, Cines Unidos and Supercines session status and see the next connection step. Use it to confirm whether authenticated queries are available before requesting prices or seats.

Instructions

Estado de las sesiones Cinex, Cines Unidos y Supercines y siguiente paso de conexión. La cuenta Supercines es opcional: sin ella las tarifas son las públicas. No devuelve datos personales ni secretos. configured no garantiza que el proveedor no haya revocado la sesión.

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_auth_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`providers`	Yes
`connection`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered; the description goes beyond them with two useful disclosures: no personal data or secrets are returned, and 'configured' does not guarantee the provider hasn't revoked the session. That last caveat meaningfully changes how an agent should interpret the result.

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?

Four short sentences with the core purpose front-loaded and each subsequent sentence adding a distinct caveat (optional account, no secrets, revocation risk). Slightly telegraphic phrasing ('siguiente paso de conexión') but no filler.

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?

An output schema exists, so return shape need not be described, and the description still covers the interpretation caveats an agent needs for a no-argument status check. Only a clearer statement of when to call it 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 takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The optional-Supercines remark is about account state, not an argument, so it does not conflict with the empty schema.

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?

The description names the exact resource (session status for Cinex, Cines Unidos and Supercines) plus an extra deliverable, the 'siguiente paso de conexión'. That is specific enough to distinguish it from the data-fetching siblings like get_showtimes or get_ticket_prices, though it never uses an explicit verb (e.g. 'returns'/'reports'), leaving the action slightly implicit.

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?

It implies the tool is consulted to find out whether connections are live and what to do next, and the note that the Supercines account is optional (public rates without it) is genuine decision-relevant context. However, there is no explicit 'use this when' or named alternative, so the agent must infer the trigger condition.

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

Deploy Server