Skip to main content
Glama

Android Developer MCP by Nova (CIVAI)

start_browser_auth

Open Play Console sign-in only when needed. If the saved session is still valid, this tool returns success immediately and does not open the viewer. Call session_status first. Use force_reconnect only when the user explicitly wants to wipe the saved cookie and sign in again (destructive).

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

Input Schema

NameRequiredDescriptionDefault
force_reconnectNoDESTRUCTIVE: delete the saved session cookie for this tenant, then open the viewer for a fresh sign-in. Do not set true unless the user explicitly asks to sign out / reconnect / clear session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. Added
  22. Removed
  23. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries full weight and does reasonably well: it discloses the idempotent short-circuit (returns success without opening the viewer when the saved session is valid) and flags force_reconnect as destructive. It does not describe what the sign-in flow requires of the user (interactive browser step, timeout, blocking behavior), which is the main remaining gap for a no-annotation tool.

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?

Front-loaded with the core action and the 'only when needed' qualifier, then the precondition, then the destructive caveat. Slight redundancy with the schema's force_reconnect text, but the warning repetition is defensible for a destructive flag.

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-param tool with no output schema or annotations, the definition covers gating, ordering, and destructive scope adequately. The only omission is how the interactive sign-in behaves (blocking, timeout, failure modes), which is minor at this complexity.

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% and the parameter description already spells out the DESTRUCTIVE semantics and the explicit-user-request guard. The description reinforces this in prose but adds no new syntax or behavioral detail beyond the schema, so the baseline 3 applies.

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?

States a specific action (open Play Console sign-in) and scopes it as conditional ('only when needed'), so an agent can distinguish it from session-checking or rollout tools. It does not name a sibling alternative outright, but the precondition reference to session_status makes the role clear.

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?

Explicit ordering guidance ('Call session_status first'), an explicit when-not ('only when needed', skips viewer if session is valid), and a gated condition for the destructive path ('only when the user explicitly wants to wipe the saved cookie'). This covers when, when-not, and precondition in three sentences.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources