Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
keyYesPath to the requester/owner private key file, passed as --key.
relayYesRelay URL used to connect the MCP server, passed as --relay.

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
acp_delegate_taskC

Delegate one task to an ACP worker and return the verified deliverable plus an audit summary.

acp_delegate_multiB

Delegate one task to several workers. race returns the first verified deliverable. quorum returns the matching verified digest.

acp_verify_audit_bundleC

Verify a bilateral AuditBundle and return the verification report.

acp_create_inviteC

Sign an acp-invite token for this server owner.

acp_revoke_tokenC

Sign a RevocationNotice and record it in this server registry.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct action: delegation (single vs multi), audit verification, and token lifecycle (create invite vs revoke). The only pair that could be confused is acp_delegate_task vs acp_delegate_multi, but the descriptions clearly differentiate single-worker vs race/quorum semantics.

Naming Consistency5/5

All five tools use a consistent acp_ prefix followed by a verb_noun pattern (revoke_token, delegate_task, delegate_multi, verify_audit_bundle, create_invite). The convention is uniform and predictable throughout.

Tool Count4/5

Five tools is a lean but reasonable scope for a delegation/audit platform, and each tool has a clear purpose. However, the surface feels slightly under-provisioned given the platform's apparent breadth (no status, listing, or worker-discovery tools).

Completeness3/5

Delegation is covered with single and multi variants, and audit verification plus token creation/revocation exist. But there is no way to query task status/results later, list or inspect the token/invite registry, discover or register workers, or cancel a delegation — notable lifecycle gaps for an agent workflow.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive