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

Tools

Functions exposed to the LLM to take actions

NameDescription
nowA

Current UTC time as ISO-8601.

calcA

Evaluate a safe arithmetic expression (e.g. '2 + 2 * 10').

json_getA

Extract a dotted path from JSON text or an object.

json_setB

Set a dotted path in JSON text or an object and return the document.

json_mergeB

Merge a JSON object at a dotted path (empty path merges at the root).

http_getB

HTTP GET a URL. Disabled unless allow_http is enabled.

list_dirA

List a directory sandboxed to the workflow workspace (dotfiles skipped).

read_fileA

Read a UTF-8 text file sandboxed to the workflow workspace.

write_fileA

Write a UTF-8 text file sandboxed to the workflow workspace.

run_workflowB

Run a ReadyAgents workflow file under the server workspace.

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

Each tool has a clearly distinct purpose: time, arithmetic, JSON path operations, HTTP GET, file directory listing/read/write, and workflow execution. There is no meaningful overlap that would cause an agent to misselect.

Naming Consistency3/5

Most tools follow a noun_verb or verb_noun underscore pattern like json_get and read_file, but now and calc are single-word exceptions. The mixed conventions are still readable and predictable enough, though not fully uniform.

Tool Count5/5

Ten tools is a well-scoped size for a general-purpose workflow utility server. Each tool serves a distinct functional area without unnecessary bloat or redundancy.

Completeness4/5

The toolset covers core utility operations: time, arithmetic, JSON manipulation, HTTP retrieval, file access, and workflow execution. Minor gaps exist such as no JSON delete or file delete, but these are workable for most workflow automation scenarios.

Maintenance

ActivityMaintained
ResponsivenessResponsive