Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FURLEN_API_KEYYesYour Furlen API key (required, with data:read and renders:write scopes).
FURLEN_BASE_URLNoBase URL for the Furlen API.https://furlen.pro

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
furlen_public_dataA

Fetch a real public dataset by describing it in plain English — no CSV needed. Pulls from the World Bank, IMF WEO, FRED, Eurostat, UN Comtrade, WHO, and company filings (SEC EDGAR, ESEF, DART, EDINET). Returns the rows, a ready-to-use csv string you can pass straight to furlen_render, and provenance naming the exact indicator and source. If no connected source covers the subject it says so rather than guessing — a 422 with code 'subject_unsupported' means the data does not exist here, not that the request was malformed, so do not retry it reworded.

furlen_renderA

Turn CSV data into an animated, claim-verified data-story video. Runs Furlen's full pipeline (profile → insights → AI story → verification → render) and returns a render id to poll with furlen_render_status.

furlen_render_statusA

Check a Furlen render job. Returns status (queued → running → completed | failed), progress, and a downloadUrl when completed. Renders typically take 30–90 seconds; poll every few seconds.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool serves a distinct purpose: fetching data, rendering a video, and checking render status. There is no functional overlap between them.

Naming Consistency5/5

All tools follow a consistent 'furlen_<noun>' pattern with clear, descriptive names. The naming convention is uniform and predictable.

Tool Count5/5

With only 3 tools, the set is tightly scoped to the core workflow (fetch, render, poll). Each tool is essential and no tool feels redundant or missing.

Completeness5/5

The tool surface covers the entire data-to-video pipeline: data fetching, render initiation, and status polling. No obvious gaps exist for the stated purpose.

Maintenance

ActivitySlowing
ResponsivenessNo issues