Skip to main content
Glama
loda-lang

LODA API MCP Server

Official
by loda-lang

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LODA_API_BASE_URLNoLODA API endpoint overridehttps://api.loda-lang.org/v2

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_sequenceC

Get details about an integer sequence by ID (e.g. A000045)

search_sequencesC

Search for integer sequences by keywords, ID, or name.

get_programC

Get details about a LODA program by ID (e.g. A000045)

search_programsC

Search for LODA programs by keywords, ID, or name.

eval_programC

Evaluate a LODA program and return sequence terms.

submit_programC

Submit a new LODA program for a sequence.

get_statsC

Get statistics summary for the LODA project.

get_submittersB

List all submitters and their number of programs.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. For example, eval_program evaluates programs, get_program and get_sequence retrieve specific resources, search_programs and search_sequences perform searches, and submit_program handles submissions. The descriptions clearly differentiate between programs and sequences, preventing misselection.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, such as eval_program, get_program, search_sequences, and submit_program. This predictability makes it easy for agents to understand and use the tool set without confusion from mixed conventions.

Tool Count5/5

With 8 tools, the server is well-scoped for managing LODA programs and sequences. Each tool earns its place by covering distinct operations like evaluation, retrieval, searching, submission, and statistics, without being overly sparse or bloated for the domain.

Completeness4/5

The tool set provides strong coverage for core workflows, including CRUD-like operations (e.g., get, search, submit) and evaluation. A minor gap is the lack of update or delete tools for programs or sequences, but agents can still work effectively with the available tools for most tasks in the LODA domain.

Maintenance

ActivityInactive
ResponsivenessNo issues