Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MACP_AGENT_IDNoThe MACP agent this server acts as. With dev-agent auth it is also the bearer token. With MACP_AUTH_TOKEN it is the identity the runtime must bind the token to.mcp-agent
MACP_AUTH_TOKENNoBearer token issued by the runtime. When unset, dev-agent auth is used, which needs a runtime started with MACP_ALLOW_INSECURE=1.
MACP_TLS_CA_FILENoPEM bundle for a private CA. Cannot be combined with MACP_ALLOW_INSECURE.system trust
MACP_ALLOW_INSECURENo`1`/`true`/`yes`/`on` uses plaintext gRPC. For a local runtime only.off
MACP_DEFAULT_TTL_MSNoSession TTL used when `start_session` is called without `ttl_ms`.300000
MACP_REPLAY_IDLE_MSNoHow long a history read waits for the next envelope before treating the replay as complete.1000
MACP_RUNTIME_TARGETNoRuntime gRPC address (`host:port`).127.0.0.1:50051

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

These tools let you run or join a MACP Decision session (macp.mode.decision.v1): a bounded, auditable vote among named agents that ends in one binding Commitment. You act as the MACP agent named in the you / sender fields of tool results.

Typical loop:

  1. start_session (initiator) -> share the returned session_id with the other participants.

  2. propose an option; participants evaluate (optional) and vote on it.

  3. get_session to see proposals, votes and the majority winner.

  4. commit (the initiator) to resolve the session with the outcome.

  5. get_commitment returns the binding outcome and its RFC-MACP-0013 commitment hash; verify recomputes that hash from the payload bytes the runtime recorded.

To join a session someone else started, you only need its session_id and to be a participant. The runtime enforces membership, ordering and identity; a rejected action returns an error.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
commitA

Resolve the session with a binding Commitment (normally the initiator).

After this the session is RESOLVED and accepts no further messages.

evaluateB

Record a scored assessment of a proposal before voting (optional step).

get_commitmentA

Return a resolved session's binding Commitment and its RFC-MACP-0013 hash.

found is false while the session is still open. payload_b64 is the exact Commitment payload bytes the runtime recorded; commitment_hash is computed over them.

get_sessionA

Show a session's state, participants, proposals, evaluations, votes and winner.

Reads the runtime's session history, so it includes every participant's messages.

proposeC

Put an option up for decision in a session.

start_sessionA

Start a new MACP Decision session with this agent as initiator.

Returns the new session_id; share it with the other participants so they can join.

verifyA

Check a commitment hash by recomputing it (RFC-MACP-0013).

Pass exactly one of session_id or payload_b64. outcome is match, mismatch, or cannot_verify (the payload itself is not hashable under the label).

voteA

Cast this agent's vote on a proposal. One vote per agent per proposal.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Each tool maps to a distinct step in the decision lifecycle (start, propose, evaluate, vote, commit) plus read-side tools (get_session, get_commitment, verify). The boundary between commit, get_commitment, and verify is slightly subtle—all involve commitments—but descriptions clarify that one writes, one retrieves, and one recomputes a hash. One or two tools could still be momentarily confused by an agent skimming names.

Naming Consistency4/5

The set uses verb-based names throughout, split between bare verbs (commit, evaluate, propose, verify, vote) and get_-prefixed reads (get_session, get_commitment). This is a coherent and readable convention, with the get_ prefix sensibly marking read-only operations. Minor deviation from a strict verb_noun pattern keeps it from a 5.

Tool Count5/5

Eight tools is well-scoped for a decision protocol covering initiate, propose, evaluate, vote, commit, and audit. Every tool corresponds to a real step or verifiable artifact, with no redundancy or filler.

Completeness3/5

The write/read lifecycle is largely covered, but start_session instructs the initiator to share the session_id so others can join, yet no join_session tool exists—an apparent dead end for non-initiator participants. There is also no way to list or discover active sessions, which limits usability in multi-party flows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues