Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

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

Sjothr lets a company tokenize its business and raise capital in USDC on Base. Each campaign has a fixed token supply and its own capital vault; backers pay from their own wallet, token holders vote on staged capital release, and a missed goal is refunded. Use sjothr_campaigns for the public campaigns, sjothr_campaign for one campaign, sjothr_rules for fees, capital release and refunds, and search then fetch for the guides (tokenizing a company, company valuation, tokenized equity, alternatives to crowdfunding and ICOs). This server is read-only and never holds keys: creating a campaign, buying and voting are signed by the user's own wallet on the site.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
sjothr_campaignsB

Public fundraising campaigns on Sjothr: company token, state, funding goal and capital raised in USDC, deadline and public record page.

sjothr_campaignA

Public record of one Sjothr campaign by campaign id: token, vault, funding goal, capital raised, deadline, state and dossier reference.

sjothr_rulesB

Rules of a Sjothr raise: who pays which fee, how capital is released in stages by token-holder votes, when backers are refunded, and the risks.

searchA

Search Sjothr campaigns and guides (tokenize a company, raise money for a startup, tokenized equity, milestone-based funding); returns ids for fetch.

fetchB

Full record of one Sjothr campaign or full text of one guide, by id (from search).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 5 tools

Disambiguation4/5

Most tools target clearly different things: list campaigns, get one campaign, get raise rules, search, and fetch-by-id. The main risk is sjothr_campaigns vs sjothr_campaign, which differ by a single letter and rely on the descriptions to distinguish list from single-record. search/fetch are cleanly paired since search explicitly returns ids for fetch.

Naming Consistency3/5

The three domain tools use a consistent sjothr_<noun> prefix, but search and fetch are bare generic verbs with no namespace, creating a mixed convention. All names are snake_case and readable, but the set is not a single predictable pattern.

Tool Count4/5

Five tools is reasonable for a read-only public-record server, and each has a defensible role. It is on the thin side given the surface spans both campaigns and guides, but nothing is redundant.

Completeness4/5

The read-only lifecycle (browse list, get detail, get rules, search, fetch full text) is covered, and search+fetch together handle guides. Minor gaps exist: no way to list guides directly or filter campaigns by state/token without going through search.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues