Skip to main content
Glama

Ouvrir Connexion

ouvrir_connexion

Opens a Chromium window for Shibboleth authentication and captures the session so later Evento API calls can reuse it; set a maximum wait time in seconds.

Instructions

Ouvre un Chromium sur la connexion Shibboleth et capture la session.

La fenêtre se ferme une fois connecté ; la session capturée est réutilisée par les appels suivants. delai : attente maximale en secondes.

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

Input Schema

NameRequiredDescriptionDefault
delaiNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does add real behavior: the window auto-closes once connected and the session persists for later calls. It still omits key traits such as whether interactive login is required, whether the call blocks, and what happens if the timeout expires.

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?

Two short sentences plus a parameter note, front-loaded with the core action and the session-reuse consequence. No wasted wording, though the parameter note is tacked on rather than integrated.

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

Completeness3/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 values need not be described, and the parameter surface is minimal. Still, for an interactive browser-login tool the description should state the prerequisite for credentials or user action and the timeout failure mode.

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 0%, so the description must compensate, and it does define 'delai' as the maximum wait in seconds with a clear unit. It fails to mention that the parameter is optional (default 180) or what behavior results from a timeout.

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 gives a concrete verb and resource: opening a Chromium instance on the Shibboleth connection and capturing the session. It clearly separates this from polling or data tools, though it does not explicitly distinguish itself from the related session-import sibling.

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?

The sentence 'la session capturée est réutilisée par les appels suivants' implies this must run before other calls, which is useful implicit guidance. However, there is no explicit when-to-use or when-not-to-use instruction, and no alternative is named.

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