Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SUBQ_API_KEYYesBearer API key for the SubQ API. Required for tool calls; the server still starts without it.
SUBQ_BASE_URLNoBase URL of the SubQ API.https://api.subq.ai
SUBQ_SNAP_MODELNoSnap model id to request. Can be overridden per call with the tools' optional model argument.subq-snap-1.1

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
snap_decideA

Ask SubQ's Snap decision model one or more typed questions (choice, score and/or noul) about a state in a single call. Returns typed answers with probabilities. The state may be text or structured JSON, and up to 4 images may accompany it; every question sees the state and every image.

snap_choiceA

Ask SubQ's Snap decision model a single Choice question: pick one of 2-255 labelled options for a state. Returns the chosen option, a confidence value, and a probability for every option, under the question name "answer".

snap_scoreA

Ask SubQ's Snap decision model a single Score question: rate a state on an ordered scale of 2-10 levels you define. Returns a probability-weighted score (it can fall between levels), the level legend, per-level probabilities, and a confidence value, under the question name "answer".

snap_noulA

Ask SubQ's Snap decision model a single Noul question: is a proposition about a state true? Returns a calibrated probability (0..1) under the question name "answer".

snap_list_modelsA

List the model IDs available to the configured SubQ API key (GET /v1/models, OpenAI-compatible shape). Use a returned id with the endpoint that supports that model; the Decisions tools in this server need a decision model such as subq-snap-1.2.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation3/5

snap_decide is a batch superset of snap_choice, snap_score, and snap_noul, so for any single-question request two tools are valid selections. The descriptions do clarify the split (batch vs. single typed question) and the three single-question tools are distinct from each other, but the redundancy creates a real selection decision the agent must reason through each call.

Naming Consistency4/5

All tools share a clean 'snap_' prefix and snake_case, so the set reads as one family. The only wrinkle is that snap_decide/snap_list_models use verbs while snap_choice/snap_score/snap_noul are named after question types rather than actions, a minor convention mix.

Tool Count5/5

Five tools is well-matched to a focused decision-inference API: one per question type, one batch entry point, and one discovery tool. Nothing feels padded and nothing essential is obviously absent.

Completeness4/5

The surface covers all three question types, a combined multi-question call, and model discovery, which is solid lifecycle coverage for a stateless inference API. Minor gaps: no model-detail/usage or credential-validation tool, and it is unclear how a caller passes a listed model ID into the decision tools, which may be a dead end after snap_list_models.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues