Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_widget_config

Fetch the current project's widget configuration (display name, branding, allowed origins) to diagnose why the widget shows default branding instead of project settings. Requires an API key.

Instructions

Fetch the widget configuration for the currently-set project: display name, branding (colors / logo / font), and allowed origins. Useful for diagnosing why the widget shows defaults instead of project branding. Requires rift_set_api_key first.

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_get_widget_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present the description must carry the behavioral load, and it does disclose the key facts: this reads config for the currently-set project (a global-state dependency), it requires prior API-key setup, and it lists exactly which values come back. It omits failure behavior when no project is set or the key is missing.

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: what it returns, why you would call it, and the prerequisite. Nothing is redundant and the payload contents are front-loaded.

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 zero-parameter read tool with no output schema, the description covers what is returned and the setup dependency well. It could be complete with a note on what happens when no API key or project is configured.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline applies. The description correctly frames the implicit 'currently-set project' scoping that stands in for a parameter.

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 (fetch) and resource (widget configuration) and enumerates the returned fields: display name, branding colors/logo/font, and allowed origins. It does not explicitly differentiate itself from the closest sibling, rift_widget_snippet, which also touches widget setup, so it falls short of a full 5.

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 a concrete use case (diagnosing why the widget shows defaults instead of project branding) and a prerequisite (call rift_set_api_key first). It stops short of stating when not to use it or naming an alternative tool for other widget tasks.

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