Skip to main content
Glama
Sign In

Kivel

by io.kivel
OverviewDiscussionsAdmin

finish_login

Read-onlyIdempotent

Wait (up to 25 seconds per call) for the human to approve the login from start_login. Returns status pending, denied, expired, or approved with the API key and MCP settings to save in your client config.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deviceCode": "<deviceCode>"
    },
    "name": "finish_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceCodeYesdeviceCode from start_login.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent read, and the description adds substantive behavior beyond them: a 25-second wait bound per call and the four possible terminal/pending statuses. It stops short of saying what to do with each status or how many times to poll.

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?

Two tight sentences with the wait bound and return values front-loaded; essentially no waste, though the status list could be formatted more scannably.

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?

With no output schema, the description usefully enumerates return statuses and notes that the approved case yields the API key and MCP settings. The only gap is guidance on how to act on each status.

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 schema already describes deviceCode as coming from start_login, so the description adds no new meaning about the parameter. Baseline 3 applies.

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?

States a specific action (wait for the human to approve the login) and anchors it to the sibling tool start_login, so an agent knows exactly which step of the login flow this is.

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 reference to 'the login from start_login' and 'up to 25 seconds per call' makes the call ordering and the need to re-invoke on pending clear by implication, but no explicit when-not or retry instruction is given.

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

All Kivel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources