Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOOPING_DIRNoDirectory used for relative Looping file paths. Defaults to ~/Documents/Looping.

Instructions

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

Read and edit Looping (.loo) MCD files: entities, associations, links, attributes; export MLD, MPD and SQL. Edits keep .bak. Paths: absolute, ~/..., or relative to the working folder /root/Looping (set LOOPING_DIR to change it). Results give the full path of the file to open in Looping.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
loo_readA

Read a .loo file and return entities, associations, links as JSON.

loo_newB

Create a new .loo file, optionally filled from a spec {entities:[{name, attributes, x?, y?}], associations:[...], links:[{entity, association, card}]}.

loo_apply_specC

Add every object of a spec (same shape as new) to an existing file.

loo_add_entityD

Add an entity.

loo_add_associationC

Add an association (relation).

loo_add_linkC

Link an entity to an association with a cardinality (0,1 / 1,1 / 0,n / 1,n).

loo_set_cardC

Change the cardinality of an existing link.

loo_remove_linkB

Remove the link between an entity and an association.

loo_add_attributeC

Add an attribute to an entity or association.

loo_update_attributeC

Rename an attribute or change its type / primary key flag.

loo_remove_attributeD

Remove an attribute.

loo_renameC

Rename an entity or association.

loo_moveC

Move an entity (top-left corner) or association (centre).

loo_removeC

Delete an entity or association and its links.

loo_mldC

Return the logical model (MLD) as text.

loo_mpdB

Return the physical model (MPD) as Markdown; also write it to out when given.

loo_sqlB

Return the SQL DDL script; also write it to out when given.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.7/5.0

Scored across 17 tools

Disambiguation4/5

Most tools have a clearly distinct target: add/remove/update for entities, associations, links, and attributes are cleanly separated, and the model-export tools (loo_mld, loo_mpd, loo_sql) are unambiguous. The only real overlap is loo_new versus loo_apply_spec, since a new file can already be populated from a spec, and loo_set_card sits close to loo_add_link, but the descriptions distinguish them adequately.

Naming Consistency4/5

All 17 tools share a single loo_ prefix and snake_case body, with a strong verb_noun pattern (loo_add_entity, loo_remove_link, loo_update_attribute, loo_apply_spec). A handful of names drop the verb form (loo_new, loo_read, loo_mld, loo_mpd, loo_sql), which are noun-like but still readable and predictable given the domain.

Tool Count4/5

17 tools is slightly above the ideal 3-15 band but is justified by a genuinely broad editor surface covering four object types (entity, association, link, attribute) plus three model exports. Each tool maps to one concrete operation, so nothing feels padded, though a couple of operations could be merged.

Completeness4/5

The lifecycle is well covered: create opening a file, full add/update/remove for entities, associations, links, and attributes, plus read-back and derived MLD/MPD/SQL output. Minor gaps remain—no file deletion or listing, no bulk edit/clear, and no way to change entity/association properties beyond rename or move.

Maintenance

ActivityMaintained
ResponsivenessOutdated data