Skip to main content
Glama
Sign In
UCA MCP

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Iniciar Sesión Institucional UCA

uca_iniciar_sesion

Starts or renews the institutional UCA session by opening a browser, returning SESION_ACTIVA if already active; use it only after a session-expired error or to sign in or switch accounts.

Instructions

Inicia o renueva la sesión institucional abriendo el navegador. Si ya hay una sesión activa responde SESION_ACTIVA (ya está iniciada) sin abrir el navegador. NO hace falta llamarla antes de consultar: cada herramienta renueva la sesión sola. Usar solo si una consulta devolvió error de sesión expirada o si el usuario pide iniciar sesión o cambiar de cuenta.

Input Schema

NameRequiredDescriptionDefault
forzar_reloginNoSi es true, purga la sesión previa y el perfil del navegador para permitir ingresar con otra cuenta @uca.edu.ar (por defecto: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / forzar_relogin / default
      Removed value: -false
    • changedInput schema / properties / forzar_relogin / description
      Previous value: -"Si es true, purga la sesión previa y el perfil del navegador para permitir ingresar con otra cuenta @uca.edu.ar"New value: +"Si es true, purga la sesión previa y el perfil del navegador para permitir ingresar con otra cuenta @uca.edu.ar (por defecto: false)"
  2. Changed3 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "estado": {
-      "type": "string"
-    },
-    "mensaje": {
-      "type": "string"
-    },
-    "usuario": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "estado",
-    "mensaje"
-  ],
-  "type": "object"
-}New value: +null
  3. First observedv1.0.6

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, and the description is consistent with all three while adding real context: it opens a browser window, returns a SESION_ACTIVA sentinel instead of launching the browser when a session exists, and that session renewal happens implicitly elsewhere. It stops short of describing what happens on login failure, timeout, or user cancellation in the browser flow.

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?

Four short sentences, front-loaded with the action, then the sentinel behavior, then the 'no need to pre-call' warning, then the trigger conditions. No filler and no repetition of the title.

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 one optional parameter and no output schema, the definition covers the invocation decision and the sentinel return fully. It leaves open the success return value and failure/timeout outcomes of the browser flow, which the absent output schema would otherwise have carried.

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% and forzar_relogin is fully documented in the schema, including its purge behavior and the @uca.edu.ar constraint. The description only alludes to it indirectly via 'cambiar de cuenta', so it adds no syntax or format detail beyond the structured field.

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 ('inicia o renueva la sesión institucional') plus the mechanism ('abriendo el navegador'), which cleanly separates it from every sibling, all of which are data-query tools. An agent can identify this as the auth/bootstrap tool without opening the schema.

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?

Explicitly states when NOT to call it ('NO hace falta llamarla antes de consultar: cada herramienta renueva la sesión sola') and the two narrow conditions that do trigger it ('error de sesión expirada' or the user asking to log in / switch account). This is a textbook when/when-not/alternative disclosure.

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