Skip to main content
Glama
Brightspace Facultad MCP

Brightspace Facultad MCP

iniciar_sesion

Opens a dedicated browser to sign in to Brightspace and complete MFA, then returns after starting the session so you can check connection status.

Instructions

Abre un navegador dedicado para ingreso y MFA en modo visible. En modo sin ventana, usar login desde una terminal gráfica con el cliente MCP cerrado. Devuelve pronto; consultar estado_conexion después.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already mark it as a mutating, open-world, non-destructive operation, and the description adds genuinely new detail: it launches a visible browser, it returns early instead of blocking, and the caller must check estado_conexion afterwards. It does not say what happens if the browser fails to open or if the session is already authenticated.

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?

Three short sentences, front-loaded with what it does, followed by the headless fallback and the follow-up action. Nothing is wasted, and the telegraphic 'Devuelve pronto' still lands clearly.

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 the return value need not be explained, and with no parameters the definition covers the operational facts that matter: visible-browser requirement, the headless workaround, and the follow-up call. It is slightly short on failure modes and on what an already-authenticated state means.

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?

There are no parameters, so the schema imposes no burden and the baseline is 4. The description adds no parameter meaning because none exists, and none is needed.

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 states a concrete verb and resource: opening a dedicated browser for login and MFA in visible mode. It is clearly distinct from the sibling estado_conexion, which it names as the polling endpoint, though it never says explicitly that it is the authentication entry point.

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 says when to use it (login and MFA) and gives an explicit alternative for the windowless case: log in from a graphical terminal with the MCP client closed. What it does not say is whether a prior session makes the call unnecessary or when to prefer another login path.

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