Skip to main content
Glama

Press5 launch pad

Finish signing in

login_check

Check whether the person approved the sign-in from login_start. Call it every few seconds after they say they have pressed Approve. Returns the token once.

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": {
      "device_code": "<device_code>"
    },
    "name": "login_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
device_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the single readOnlyHint=false annotation: the call is a poll, it should be repeated, and it 'Returns the token once,' which tells the agent the terminal success condition. It leaves open what a pending or expired response looks like and whether the device_code is single-use, which matters for a token-issuing call.

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?

Three short sentences, front-loaded with the purpose, then the polling instruction, then the return behavior. Nothing is wasted and no sentence restates the title.

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?

For a one-parameter polling tool with no output schema, the definition covers origin of the input, cadence of invocation, and the terminal return value. The remaining detail (pending-state response, expiry) is minor relative to the tool's simplicity.

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 0% for the single required parameter, so the description must carry the meaning; it does partly by locating device_code as coming 'from login_start,' implying the value is the one returned by that sibling. It gives no format, lifetime, or reuse semantics, so the gap is only partially closed.

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 verb and resource ('Check whether the person approved the sign-in') and explicitly ties it to the login_start flow, so the agent can distinguish it from login_start and the site-management siblings without opening the schema.

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?

Gives concrete when-to-use guidance and a polling cadence ('Call it every few seconds after they say they have pressed Approve'), which is exactly what an agent needs to sequence this call. It does not say when to stop polling on failure, how long the code stays valid, or what to do if the user has not yet approved, so it stops short of full 5-level guidance.

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