Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENTDRAFT_API_KEYYesYour AgentDraft agent API key, beginning with avs_live_…
AGENTDRAFT_BASE_URLNoOptional base URL for the AgentDraft backend. For local development against a dev backend, set this to http://localhost:8080.

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
whoamiA

Confirm the configured AGENTDRAFT_API_KEY is valid and return the calling agent's identity, priority, scopes, and the owner's timezone (so a client can render slots in the owner's zone).

get_availabilityA

List slots open to the calling agent within [start, end).

Times are ISO 8601 strings (2026-06-01T14:00:00Z). The result is filtered through the user's focus blocks, buffer rules, and any currently-active holds across sibling agents.

create_holdA

Reserve a slot tentatively. Holds expire automatically (30s TTL by default). A subsequent commit_booking on the same slot promotes the hold to a final booking.

Optional title and invitee ({name, email, notes}) record who the slot is for; both carry through to the eventual commit.

Returns an outranked payload if a higher-priority agent already holds or has committed the slot inside the bump window.

release_holdB

Release a previously-created hold so other agents can claim the slot before the TTL expires.

commit_bookingA

Finalize a booking. This is the atomic compare-and-swap at the slot level — exactly one agent succeeds per slot in any race window. Returns an outranked payload on 409.

Optional title and invitee ({name, email, notes}) record who the slot is for; both are echoed back and shown to the owner in the dashboard.

Set with_conferencing=True to attach a video meeting link to the committed booking; the link is returned under conferencing.

cancel_bookingA

Cancel a previously-committed booking owned by the calling agent. The slot becomes available to other agents immediately.

request_approvalA

Open a human sign-off request and return immediately.

action_type is a namespaced lowercase string such as deploy.production, mailbox.send_external, or billing.refund. summary is the one line a reviewer reads first; evidence is the structured context they need to decide (target, amount, exact draft). Returns {approval_id, status, expires_at}. Requires the approvals:request scope.

get_approvalA

Read the current state of one approval request: pending, approved, denied, or expired, plus the reviewer's note once resolved. Safe to poll; it never blocks.

wait_for_approvalA

Wait for a human decision, bounded to 120 seconds.

The timeout is clamped to [1, 120] and the poll interval to [1, 30] so no MCP host is left hanging. If the request is still pending when the timeout lapses, the result carries status: "pending" and timed_out: true; call get_approval or wait_for_approval again to keep waiting. Proceed only when the status is approved — denied, expired, and pending all mean stop.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct resource+action: holds (create/release), bookings (commit/cancel), availability, identity, and approvals (request/get/wait). The only potentially close pair, get_approval vs wait_for_approval, is explicitly differentiated by non-blocking vs blocking behavior in their descriptions.

Naming Consistency4/5

Nearly all tools follow a clean snake_case verb_noun pattern (get_availability, create_hold, commit_booking, request_approval). The single deviation is 'whoami', which is a fixed phrase rather than a verb_noun construction, but it is idiomatic and unambiguous.

Tool Count5/5

Nine tools is well within the ideal 3-15 range and every tool maps to a concrete step in the booking or approval workflow. No tool feels redundant or filler.

Completeness4/5

The booking lifecycle is fully covered (availability, hold create/release, commit, cancel) and approvals support request/get/wait. Minor gaps remain: there is no list_approvals to enumerate pending requests and no way to withdraw/cancel an approval request, but agents can work around these with get_approval.

Maintenance

ActivityMaintained
ResponsivenessNo issues