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.

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_actsA

Search ARLIS for acts and return their titles, URLs and metadata. Latest versions only, in ARLIS's default order. Use get_act to retrieve the text. Use only the search_string parameter; others default to what you will need in 99% of cases. Don't use optional parameters without a reason.

get_actA

Fetch one ARLIS act URL and save it as a local markdown file.

Writes the act's plain-text metadata followed by its full text as markdown to <output_dir>/.md (default directory .arlis under PLUGIN_DATA, or the server working directory if PLUGIN_DATA is unset or empty). Returns only the absolute saved path, the metadata line range and a short line-numbered heading structure.

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

Disambiguation5/5

The two tools have clearly distinct roles: search_acts discovers acts and returns metadata/URLs, while get_act retrieves and saves the full text for a specific act URL. There is no realistic ambiguity about which tool to use for discovery versus retrieval.

Naming Consistency5/5

Both names follow the same snake_case verb_noun convention: search_acts and get_act. The pattern is predictable and directly reflects each tool's action.

Tool Count4/5

Two tools are slightly thin for the generic 3–15 range, but they map cleanly to the server's narrow search-and-retrieve purpose. Neither tool feels redundant or extraneous.

Completeness4/5

The surface covers the core workflow of finding an act and fetching its text, with metadata and local file output. Minor gaps exist around pagination, version handling, or more structured retrieval, but the main use case is supported.

Maintenance

ActivityActive
ResponsivenessNo recent community issues