Skip to main content
Glama

Press5 launch pad

Sign in by email

login_start

Start signing in to the Press5 launch pad when you have no token. Press5 emails the person a link to approve this tool (it also creates a free account for a new email). Then call login_check.

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": {
      "email": "<email>"
    },
    "name": "login_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe person's email address
clientNoYour name, shown to the person, e.g. "Claude Code"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare openWorldHint=true, so the description carries most of the burden and does it well: it discloses that an out-of-band email with an approval link is sent, that a free account is created for new emails, and that the operation is asynchronous and requires a follow-up call to login_check. It does not cover link expiry, rate limits, or what this call itself returns, which keeps it below a 5.

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 with the precondition front-loaded, followed by the side effect and the next-step hand-off. Nothing is redundant and the ordering matches how an agent would reason about the call.

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 two-parameter authentication entry point with no output schema, the description conveys the full flow: trigger, out-of-band approval, account creation side effect, and the required follow-up call. The main remaining gap is what login_start itself returns before the approval completes, which an agent might want to know.

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%, so both parameters are already documented in the schema (email as the person's address, client as the name shown to the person). The description adds no additional parameter meaning, so the 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?

The description names a specific verb and resource ("Start signing in to the Press5 launch pad") and immediately scopes it with the trigger condition "when you have no token." It also distinguishes itself from the sibling login_check by stating that login_check is the follow-up step, so an agent can tell the two apart without opening either 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?

The condition "when you have no token" tells the agent exactly when this tool applies, and "Then call login_check" gives the required next step in the flow. It stops short of explicitly saying not to call this when a token already exists, but that exclusion is strongly implied by the stated precondition.

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