Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STEMSEAL_LANGNoOptional. Set to "ko" or "en" to fix the guide language. By default, guides answer in Korean when the request contains Hangul and in English otherwise.
STEMSEAL_MODELNoOptional. When set, find_cell returns a short selection guide written for that model family's known weak spots, and call_cell repairs those input mistakes before running the cell. Example: "qwen2.5:3b".

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_cellA

Call this first whenever the user asks for a number worked out by rules: wages, salary, rates, growth, margins, prices, percentiles, calories, currency, leave days and similar. Verified cells give the exact checked answer, and small models get these wrong when computing alone. State the need in plain words. Returns the cells that fit, each with its required inputs and an input example, or an empty list when nothing fits.

call_cellA

Run a locked cell found with find_cell (use its exact name; do not guess names). Use the cell's required input keys exactly, as in its input example. Pass its input either inline as input or, for large data, as input_file (path to a JSON file holding the input object) so the data need not be retyped. Returns status ok (verified result), not_available, or invalid_input. Never invents a result. If refused, the reply's how_to_fix shows the exact input to send again.

list_cellsA

List every locked cell on this machine with what it computes and its required inputs. Cheap; use it when unsure what exists.

request_cellA

Tell the hub that you needed a calculation and no cell fit. This is how new cells get made: you get a ticket, and the cell is built as demand gathers, so come back next time. Describe the need in one or two sentences.

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 4 tools

Disambiguation5/5

Each tool has a distinct role in the workflow: list_cells browses all cells, find_cell searches by need, call_cell executes a known cell, and request_cell asks for missing functionality. The descriptions clearly separate discovery, execution, and demand requests, so misselection is unlikely.

Naming Consistency5/5

All names follow a consistent verb_noun snake_case pattern: list_cells, request_cell, find_cell, call_cell. The only variation is natural pluralization on list_cells, which is not confusing.

Tool Count5/5

Four tools is well-scoped for a verified-calculation hub: browse, search, execute, and request. Each tool has a clear purpose and earns its place, with no obvious redundancy or thinness.

Completeness4/5

The surface covers the core lifecycle: see available cells, find one matching a need, run it, and request a new one when none fits. A direct get-cell-by-name lookup independent of semantic search is a minor gap, but agents can work around it via find_cell or list_cells.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues