aafp-commons
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMMONS_HOME | No | The directory where AAFP Commons stores its data. Used to initialize and manage the local ledger. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| commons_worldA | Read the local signed world. This is safe in source posture; writing requires an initialized subject, evidence, and a digest-pinned constitution. |
| commons_queryA | Query exact packet IDs or scan a namespace prefix. An empty query scans every admitted namespace (commons/, org/, and agent/). Results are signed packets; proposals still require evidence and a digest-pinned constitution. |
| commons_getA | Read one signed packet by content address. Writing requires evidence and a digest-pinned constitution. |
| commons_assume_constitutionA | Validate the constitution selected by commons init. Constitution admission is explicit and evidence-gated; source posture must run commons init first. |
| commons_proposeB | Sign and admit one packet. Subject posture, at least one evidence reference, and an installed digest-pinned constitution are required. |
| commons_conflictsB | Read conflict IDs in the local world. Evidence and constitution rules apply to any future proposal that creates conflict objects. |
| commons_resolutionsB | Read resolution IDs in the local world. Evidence and constitution rules apply to any future resolution proposal. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The read tools are separated by scope: world reads the whole signed world, query searches by packet ID or namespace, and get retrieves one content-addressed packet. Conflicts and resolutions are clearly distinct read endpoints, though query and get could still cause minor selection hesitation.
All tools share the commons_ prefix, which establishes a strong family identity. However, suffixes mix nouns like world, conflicts, and resolutions with verbs like query, get, and propose, so the set is readable but not a uniform verb_noun convention.
Seven tools is well-scoped for a signed-packet commons governance domain. Each tool has a distinct role without redundant operations.
Core read, query, propose, and conflict/resolution read operations are covered. However, prerequisites such as commons init, evidence management, and constitution setup or updates have no MCP-visible tools, leaving meaningful gaps in the write/propose workflow.