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
demo_ordersA

Return a synthetic order book as a JSON record array. Nothing is fetched and nothing is stored — the point is the shape, so you can see what terse does to a record-shaped tool result.

demo_logsA

Return a synthetic plain-text log tail. Non-JSON on purpose: it is what terse's text tier sees, as opposed to the record array demo_orders returns.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are completely distinct: demo_orders returns a JSON array of records, while demo_logs returns plain-text log lines. Their purposes—showing structured vs. text output—are clearly separated, leaving no ambiguity.

Naming Consistency5/5

Both tools follow the same `demo_<plural noun>` pattern, using consistent lowercase snake_case and a common prefix. The naming is predictable and coherent, even though it deviates from a strict verb_noun style.

Tool Count4/5

At just two tools, the server is slightly below the typical 3-15 range, but the count is deliberate: one tool for each of terse's two data tiers. This makes the set well-scoped for its demo purpose.

Completeness5/5

The server's stated domain is demonstrating terse's handling of record-shaped vs. text-shaped results, and these two tools cover exactly that distinction. There are no missing operations or dead ends for the intended scope.

Maintenance

ActivityActive
ResponsivenessResponsive