Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DA_ADMIN_API_TOKENYesYour API token for the DA Admin API

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
da_admin_list_sourcesB

Returns a list of sources inside a folder from an organization

da_admin_get_sourceC

Get source content from an organization: can be an html file or a json file

da_admin_create_sourceA

Create source content within an organization: can be an html file or a json file

da_admin_delete_sourceB

Delete source content from an organization: can be an html file or a json file

da_media_check_statusA

Check if media index exists on a site. Returns initialization URL if not found.

da_media_refresh_cacheA

Refresh the media data cache by fetching the latest media.json. Use when media has been updated.

da_media_get_indexB

Get the complete media index (media.json) for a site. Returns all media references with timestamp.

da_media_searchC

Search and filter media items by type, document, name, alt text, unused status, or missing alt text.

da_media_get_statsA

Get media usage statistics including total count, breakdown by type, unused media count, and alt text status (filled/decorative/notFilled).

da_media_find_usageB

Find all documents using a specific media item by URL or name.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation5/5

Tools are clearly separated into two groups (da_admin for sources and da_media for media) with distinct actions. Within each group, no two tools have overlapping purposes; each performs a unique operation.

Naming Consistency5/5

All tools follow a consistent snake_case pattern with prefixes 'da_admin_' and 'da_media_'. Verbs are action-oriented (list, get, create, delete, check, refresh, get, search, find), creating a predictable naming scheme.

Tool Count5/5

10 tools is well-scoped for the domain covering source management and media metadata operations. Each tool serves a distinct purpose without unnecessary bloat or gaps.

Completeness4/5

Source tools cover list, get, create, delete, but lack an update operation. Media tools provide comprehensive operations for checking, refreshing, searching, and analyzing media, but no create or delete for media items (assuming they are managed via sources). Minor gap in source update.

Maintenance

ActivityInactive
ResponsivenessNo issues