Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_login_apple

Sign in to or create a Rift Finance account with a client-supplied Apple identity token; include displayName on first sign-in to unlock authenticated tools.

Instructions

Sign in (or sign up on first use) with an Apple identity token. The frontend obtains the idToken from 'Sign in with Apple' — authorization.id_token from AppleID.auth.signIn() on web, the identity token from ASAuthorizationAppleIDCredential on iOS, or expo-apple-authentication on RN. NOT something the agent can produce — ask the user / client for the idToken. Apple only delivers email/name on the FIRST sign-in (and only the privaterelay alias if 'Hide My Email' is on); pass displayName then. Apple-bound accounts are NOT locked to Apple — email/OTP still works for users with a non-relay email on file. After this call, all authenticated tools work.

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": {
      "idToken": "<idToken>"
    },
    "name": "rift_login_apple"
  }
}

Input Schema

NameRequiredDescriptionDefault
idTokenYesApple identity token (JWT) obtained on the frontend
referrerNoOptional referral code — propagated only on first sign-in (account creation)
displayNameNoFirst+last name composed by the client. Apple only delivers this on first sign-in — capture and forward it then.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that email/name arrive only on first sign-in, that 'Hide My Email' yields only a privaterelay alias, and that Apple-bound accounts are not locked to Apple since email/OTP still works. What it omits is session/error behavior — token expiry, failure modes, and what a successful call actually yields.

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?

The critical constraint (agent cannot produce the token) is front-loaded and each sentence adds distinct information. The platform-specific acquisition examples are dense but genuinely useful for instructing the user, though the parenthetical stack of API names is the one stretch that could be trimmed.

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 three-parameter login tool with no annotations and no output schema, the description covers the hard parts: token provenance, first-sign-in-only fields, and post-auth capability. The notable gap is that it never says what the call returns (session token, user object), which matters precisely because there is no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description goes beyond it by explaining the Apple-side constraint behind displayName ('Apple only delivers this on first sign-in — capture and forward it then') and the privaterelay alias caveat that determines whether a usable email exists. It does add some redundancy with the schema, which already states referrer and displayName are first-sign-in-only.

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 opens with a specific verb and resource: 'Sign in (or sign up on first use) with an Apple identity token,' which also encodes the dual-purpose first-use behavior. The Apple qualifier makes it immediately distinguishable from rift_login and rift_login_google without opening any 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?

It gives an explicit negative instruction — 'NOT something the agent can produce — ask the user / client for the idToken' — plus concrete frontend acquisition paths for web, iOS, and RN. It also states the downstream condition ('After this call, all authenticated tools work'). It stops short of explicitly naming rift_login_google or rift_login as the alternatives for non-Apple flows, relying on the tool name to carry that routing.

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