Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Se connecter à viraldar

connexion

Authorize the agent to access a viraldar account through a browser login page that returns the session to the MCP; call it when another tool reports the user is not connected.

Instructions

Connecte ce MCP au compte viraldar de l'utilisateur. Ouvre une page de viraldar.rayvol.net dans son navigateur, où il se connecte (Google, ou e-mail + mot de passe) pour autoriser l'agent ; la page rend la session au MCP par 127.0.0.1. L'outil attend jusqu'à 2 minutes ; s'il rend la main avant, l'utilisateur peut finir dans le navigateur (le lien reste valable 10 minutes) puis tu rappelles connexion ou qui_suis_je. À appeler quand un autre outil répond « pas connecté ». Ne demande jamais son mot de passe à l'utilisateur.

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

Input Schema

NameRequiredDescriptionDefault
forcerNoReconnecter même si une session existe déjà (changer de compte).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well: it discloses the out-of-band browser flow, the accepted auth methods, the 127.0.0.1 callback, a 2-minute wait, a 10-minute link validity, and the possibility of an early return. These are exactly the side effects and timing constraints an agent cannot infer elsewhere.

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?

It is dense but well ordered: purpose, mechanics, timeout behavior, recall path, trigger condition, then the safety rule. Every sentence carries information, though the parenthetical auth methods and callback details make it longer than strictly necessary.

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?

For a one-parameter auth tool with no annotations and no output schema, the description covers trigger, flow, timing, and recovery. The only real gap is what a successful return looks like (session confirmed, identity available), which an agent may want to know before proceeding to other tools.

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%, so the single `forcer` parameter is already documented, including its 'changer de compte' meaning. The description adds no further parameter guidance, which is the expected baseline when the schema does the heavy lifting.

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 names a concrete verb and resource: it connects this MCP to the user's viraldar account, opening a viraldar.rayvol.net page in the browser. It also implicitly separates itself from the read-only sibling 'qui_suis_je' by framing that one as a post-connection check rather than the login itself.

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?

It explicitly states the trigger condition (call it when another tool answers 'pas connecté') and gives the recovery path if the tool returns early: finish in the browser, then re-call `connexion` or `qui_suis_je`. It also states a negative rule — never ask the user for their password.

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