Skip to main content
Glama

Login

login
Idempotent

Authenticates an Orbits session through the browser; returns the current user if already signed in, or a pending link and code to authorize, then re-run to confirm.

Instructions

Inicia sesión en Orbits desde el navegador. Si ya hay sesión devuelve el usuario (status ok).

Si no, devuelve status pending con un enlace y un código que debes mostrar al usuario; cuando autorice, vuelve a llamar login para confirmar. Llamarla mientras está pendiente no inicia otro flujo.

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

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.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, so the description is not obligated to carry safety context, yet it adds real behavioral information: the two possible outcomes (existing session returns the user with status ok; otherwise status pending with a link and code), the required human-in-the-loop step, and the idempotency of repeated calls while pending. That is meaningfully more than the annotations convey.

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 ordered by importance: what it does, the success branch, the pending branch with the required action, then the anti-pattern warning. No filler, no repetition of the title, and the pending-state caveat lands last where it is most likely to be retained before a retry.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a stateful, multi-step authentication flow, the hardest category to document, and the description covers both terminal states, the user interaction step, and the retry semantics. An output schema exists, so the description is not required to describe return shapes further, and what it does say about status values is a bonus rather than a gap.

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 per the baseline this scores 4, and there is no parameter ambiguity for the description to resolve. Nothing in the prose misdescribes the (empty) input contract.

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?

Opens with a specific verb and resource ("Inicia sesión en Orbits desde el navegador") rather than restating the title alone. It immediately frames the tool as a session-checking login rather than, say, a credential-setting tool like set_user_password, so an agent can distinguish it from the sibling set.

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?

Gives explicit state-based instructions: call it, and if the status is pending, show the link and code to the user and call login again to confirm. It also anticipates the wrong move — calling again while pending does not start a second flow — which is exactly the guidance an agent needs to avoid looping or spamming the user.

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