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

Tools

Functions exposed to the LLM to take actions

NameDescription
delegateA

Delegate a coding task to cursor-agent over ACP. Never shell out to cursor-agent — use this tool only. Auto-approves every permission the agent requests, in any mode and anywhere on disk. Clarifying questions arrive as prose in result — resume with resumeSessionId to answer. Keep model (composer-2.5), fast and effort at their defaults unless the user explicitly asks. See the delegate skill.

cancelA

Best-effort cancel of an in-flight delegation by sessionId. session/cancel is advisory — the agent may finish the turn anyway, and the delegate result then carries cancelRequested. Status: cancelled, killed (agent process observed to exit), not-running (turn already ended, still resumable), not-found (id not in this process's recent session history).

doctorA

Setup diagnostics: plugin version, MCP client capabilities, cursor-agent launcher resolution. Run when delegation fails or agent.found is false.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct, non-overlapping purpose: delegate for initiating/resuming tasks, cancel for stopping in-flight work, and doctor for diagnostic checks. No ambiguity between tools.

Naming Consistency5/5

All three tool names are lowercase verbs (delegate, cancel, doctor), following a clean, consistent single-word verb pattern. Perfectly predictable.

Tool Count5/5

With exactly three tools, the server is tightly scoped to its core workflow: delegate, cancel, and diagnose. Every tool earns its place and the count feels appropriate for the purpose.

Completeness5/5

The tool set covers the full lifecycle of a delegation: starting/resuming (delegate), terminating (cancel), and troubleshooting setup (doctor). No obvious gaps for the stated domain.

Maintenance

ActivityActive
ResponsivenessNo issues