Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_get_api_endpoints

Retrieve REST API endpoint details for a Rift Finance service group, including methods, paths, authentication requirements, and request body schemas.

Instructions

Get REST API endpoint details for a service group. Returns methods, paths, auth requirements, and request body schemas.

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": {
      "service": "<service>"
    },
    "name": "rift_get_api_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesService: auth, wallet, transaction, offramp, onramp, bridge, kyc, walletconnect, merchant, notifications, signer, assets, users, deposits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden but does disclose the return payload shape, which is the key behavioral fact. It leaves out whether results reflect live services vs. static specs, what happens for an invalid service string, and whether rows are paginated or filtered.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the return contents immediately following.

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 one-parameter read-only lookup with a fully documented schema and no output schema, the description covers purpose and return contents adequately. It could add a line about auth/config prerequisites for a fully self-contained definition.

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% and the single 'service' parameter already lists all valid values, so the schema does the heavy lifting. The description only echoes 'service group' without adding selection criteria or format details 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?

The description uses a specific verb+resource ('Get REST API endpoint details for a service group') and enumerates the payload contents (methods, paths, auth requirements, request body schemas). The resource is clearly distinct from siblings like rift_get_balance or rift_get_chains, though the differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

No when-to-use guidance is given: nothing says when an agent should query endpoint specs versus the other rift_get_* tools, no prerequisites are mentioned (e.g., whether rift_set_api_url or rift_set_api_key must be configured first), and no limitations or exclusions are stated.

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