Skip to main content
Glama

Latest login outcome

login_status
Read-only

Returns the latest login outcome per profile to help diagnose failed or empty run_in_page attempts in bridge mode.

Instructions

Returns the latest login outcome per profile (as reported by the page in bridge mode). Use it when running the run_in_page script failed or returned nothing.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoOnly this profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful provenance — the data is page-reported in bridge mode, implying it depends on a live page and may be absent or stale otherwise. It does not say what an empty result means or whether it can fail, leaving the diagnostic path incomplete.

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?

Two short sentences with no filler: the what is front-loaded and the when-to-use follows immediately. Nothing could be removed without losing information.

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-optional-parameter read-only tool with full schema coverage and annotations covering the safety profile, the definition supplies what an agent needs to decide to call it. The only gap is not describing the result shape or the meaning of an empty outcome, which matters given this is a failure-diagnosis tool.

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 description coverage is 100% and the single optional `profile` parameter is already documented as "Only this profile." The description's "per profile" phrasing implies the unfiltered call returns all profiles, which is a small addition, but otherwise the schema carries the meaning.

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?

"Returns the latest login outcome per profile" gives a specific verb and resource with a clear scope, and the parenthetical identifies the data source (page-reported in bridge mode). It does not explicitly contrast with the sibling `login` tool, but the purpose is unambiguous on its own.

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?

The description states a concrete trigger condition: use it when a `run_in_page` script failed or returned nothing. That is actionable context an agent could not infer from the name. It lacks any when-not guidance or a fallback if this tool also returns nothing, so it stops short of the top band.

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