Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_widget_snippet

Generates ready-to-paste Rift sign-in widget embed code for HTML, React, or Next.js, using your project API key so developers can add authentication to a site or app.

Instructions

Return a ready-to-paste embed snippet for the Rift sign-in widget. Use this when a developer asks 'how do I add Rift to my site/app'. The output is a fully runnable code block keyed by their framework (html/react/nextjs). Each snippet uses the project's actual API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rift_widget_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoInitial mode the modal opens in. Users can still toggle between sign-in and sign-up inside the modal.signin
apiKeyNoOverride the currently-set project API key. Defaults to whichever key was set via rift_set_api_key.
frameworkNoWhere the widget will be embedded. 'html' for vanilla / any non-React framework; 'react' for a Vite/CRA React app; 'nextjs' for App Router.html

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the meaningful behavior: the output is a fully runnable code block keyed by framework, and it embeds the project's actual API key rather than a placeholder. It does not mention what happens when no API key has been set, which is the main remaining behavioral gap.

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?

Four short sentences, front-loaded with the core action and output shape, with the usage trigger placed early. The quoted developer phrasing is slightly chatty but earns its place by anchoring intent.

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?

No output schema exists, and the description compensates by describing the return value as a runnable code block keyed by framework. Combined with fully documented parameters, an agent has enough to call it correctly; only failure behavior (missing API key) is unaddressed.

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%, so the enum semantics for framework and mode are already documented. The description reinforces that snippets are keyed by framework and that the real API key is used, but adds no format or syntax detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it returns a ready-to-paste embed snippet for the Rift sign-in widget, and clarifies the output is a runnable code block. It is clearly distinct from config-style siblings, though it never names rift_get_widget_config as the alternative for retrieving settings rather than code.

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 an explicit trigger scenario: 'use this when a developer asks how do I add Rift to my site/app'. It does not state when NOT to use it or name a competing tool for adjacent needs, so it falls short of a full 5.

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