Skip to main content
Glama
kychee-com

run402-mcp

by kychee-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

verify_magic_link

Verify a magic link token to exchange for access and refresh tokens, creating the user if they don't exist. Token is single-use and expires in 15 minutes.

Instructions

Exchange a magic link token for access_token + refresh_token. Creates the user if they don't exist. Token is single-use and expires in 15 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoSix-digit email code. Required with challenge_id.
tokenNoMagic-link token. Mutually exclusive with challenge_id/code.
project_idYesThe project ID
challenge_idNoOpaque email-code challenge handle. Required with code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.13.3
    • addedInput schema / properties / challenge_id
      Added value: +{
+  "description": "Opaque email-code challenge handle. Required with code.",
+  "type": "string"
+}
    • addedInput schema / properties / code
      Added value: +{
+  "description": "Six-digit email code. Required with challenge_id.",
+  "type": "string"
+}
    • changedInput schema / properties / token / description
      Previous value: -"The magic link token from the email link URL (?token=...)"New value: +"Magic-link token. Mutually exclusive with challenge_id/code."
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "token"
-]New value: +[
+  "project_id"
+]
  2. First observedv3.6.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description fully bears the burden of disclosure. It reveals important side effects (user creation if not exist) and token properties (single-use, 15-min expiry). This goes beyond basic functionality but could mention error scenarios or return format.

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 concise sentences front-load the main action, with no superfluous information. Every sentence adds value.

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?

Given no annotations and no output schema, the description covers the core functionality, side effects, and key constraints. It is complete enough for a simple authentication tool, though missing error conditions and prerequisites.

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% with each parameter described adequately. The overall description adds only marginal context about token constraints already implied. Baseline 3 is appropriate as schema carries most of the semantic load.

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 clearly states the verb 'Exchange' and the resource 'magic link token', and specifies the output (access_token + refresh_token). This distinguishes it from the sibling tool 'request_magic_link' which likely initiates the link.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for verifying a magic link after requesting it, but does not explicitly state when to use this vs. alternatives like 'request_magic_link'. It mentions token constraints (single-use, 15-min expiry) which provide context but lacks explicit usage guidance.

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