Skip to main content
Glama

login

Signs in to Infinite Backlog by typing credentials from the IB_USERNAME and IB_PASSWORD environment variables into the form, enabling authenticated reads and edits.

Instructions

Sign in with IB_USERNAME and IB_PASSWORD from the environment.

Types them into the Infinite Backlog login form. If either value is missing, nothing is typed. Use the Playwright window instead (open_site with headless=false).

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
headlessNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.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 burden, and it does disclose two important behaviors: credentials come from environment variables, and a missing value means nothing is typed (a silent no-op rather than an error). It does not say whether a browser is launched or reused, whether it navigates before typing, how it signals success or failure, or whether credentials are masked. That leaves meaningful behavioral gaps for an auth action.

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?

Three short sentences, front-loaded with the core action and its failure mode. Nothing is padded, though the trailing alternative sentence is loosely attached and could be tightened to make clear it is a fallback path rather than part of the primary flow.

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 no explanation, and the credential sourcing and no-op-on-missing behavior are covered. However, for an authentication step the description should say whether it opens/uses a browser session and how the caller knows it succeeded, and the headless parameter is entirely undocumented. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter (headless, default null) has 0% schema description coverage and is never explained in the description. The only mention of 'headless' appears in a reference to a different tool (open_site with headless=false), which is more likely to confuse than clarify what setting this tool's headless flag does. With one undocumented parameter, the baseline of 3 does not apply and the description fails to compensate.

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 specific action: reading IB_USERNAME/IB_PASSWORD from the environment and typing them into the Infinite Backlog login form. That is a concrete verb+resource that an agent can distinguish from generic navigation tools. It stops just short of 5 because the final sentence about the Playwright window blurs whether the subject is this tool or open_site.

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 gives a clear precondition (credentials present in the environment) and names an explicit alternative (open_site with headless=false) for the case where they are not. What it does not do is explain when the tool's own headless parameter should be set one way or the other, so guidance is clear but incomplete.

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