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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
echoB

Echoes back the input message

file_readA

Reads a file from the allowed filesystem paths

file_writeB

Writes content to a file in the allowed filesystem paths

json_transformC

Transforms JSON data using a JQ-like filter

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

Disambiguation5/5

Each tool has a clearly distinct purpose: echo returns input, file_read reads files, file_write writes files, and json_transform applies a JQ-like filter. There is no meaningful overlap or ambiguity among the four tools.

Naming Consistency4/5

The set mostly follows a predictable snake_case resource_action pattern (file_read, file_write, json_transform). The only minor deviation is echo, which is a bare verb rather than a resource_action name.

Tool Count5/5

Four tools is a well-scoped size for a lightweight utility server. Each tool covers a distinct, useful operation without bloat or redundancy.

Completeness3/5

The file surface supports read and write but lacks obvious companion operations such as listing, deleting, or checking file existence. The JSON tool supports transformation but not validation or parsing, leaving notable gaps for an agent working in this utility domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues