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

Tools

Functions exposed to the LLM to take actions

NameDescription
boardagent_create_taskA

Create a new task. Priority is a color: red/orange/yellow/green/blue/white. Tasks are always created as todo (claim to start work). Requires write role.

boardagent_list_tasksC

List tasks, optionally filtered. Requires read role.

boardagent_get_taskB

Read a single task by id. Requires read role.

boardagent_update_taskC

Update a task. Metadata is merged into agent_id's namespace. Requires write role.

boardagent_delete_taskA

Delete a task by id. Requires admin role.

boardagent_claim_taskB

Claim/lock a todo task for an agent. Returns an error if unavailable. Requires write role.

boardagent_complete_taskA

Mark a task done. Only the owning agent may complete it. Requires write role.

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

Disambiguation5/5

Each tool maps to a distinct action: CRUD (create/list/get/update/delete) plus two clearly-scoped lifecycle operations (claim for locking, complete for finishing). Claim vs update are well separated by their descriptions (lock vs metadata merge), so misselection is unlikely.

Naming Consistency5/5

All seven tools share the boardagent_ prefix and follow a strict verb_noun pattern (create_task, list_tasks, get_task, delete_task, update_task, claim_task, complete_task). No mixed conventions or vague verbs.

Tool Count5/5

Seven tools is a well-scoped set for a task board, covering the essential operations without bloat. Every tool earns its place.

Completeness4/5

Full CRUD plus claim/complete lifecycle is strong, but a few natural operations are absent: releasing/unclaiming a task, reopening a completed task, and explicit assignment. These are minor gaps an agent can largely work around.

Maintenance

ActivityMaintained
ResponsivenessNo issues