Skip to main content
Glama
Sign In
Compounding MCP

Compounding MCP

by dshguilherme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

swarm_commit

Record a validated contribution with parent and semantic informed_by SHAs to trace ancestry and store evidence in Git-based swarm workflows.

Instructions

Record a validated contribution with parent and semantic informed_by SHAs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "swarm_id": "<swarm_id>",
      "worker": "<worker>",
      "parent": "<parent>",
      "informed_by": "<informed_by>",
      "message": "<message>",
      "score": "<score>",
      "validation": "<validation>"
    },
    "name": "swarm_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoreYes
parentYes
workerYes
messageYes
swarm_idYes
validationYes
informed_byYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. "Record" implies a write operation, but the description does not explain permissions, idempotency, side effects, whether the contribution is rejected if unvalidated, or what the commit produces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. However, it is too sparse for a tool with seven required parameters and no schema descriptions, so its brevity comes at the cost of missing essential structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given seven required parameters, no annotations, no output schema, and zero schema description coverage, the description is substantially incomplete. It gives only a high-level hint about two parameters and omits most of what an agent needs to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across seven required parameters. The description clarifies that parent and informed_by are SHAs and that informed_by has semantic meaning, but it leaves swarm_id, worker, message, score, and validation entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb, "Record," and a specific resource, "a validated contribution," and it names key SHA fields. It clearly identifies the core action but does not explicitly distinguish this tool from siblings such as swarm_announce or swarm_nominate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "validated contribution" implies that validation should happen first, but there is no explicit guidance on when to use this tool versus alternatives. No prerequisites or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools