Skip to main content
Glama
Repository Manager

Repository Manager

Reconcile

rm_concepts_reconcile

Coordinate concept-id claims against a central authority to prevent local ID allocation and reject mutations when the authority is unavailable.

Instructions

Reconcile (rm_concepts). Concept-id claim coordination against RMDD-16's central authority.

Repository-manager never allocates a concept id itself: every action here is a thin, MCP/CLI-neutral consumer of an injected authority port. When the central authority (scion_sdk.governance. concept_reservation) is unavailable in this environment, every mutating action refuses with a named dependency_blocked/ConceptAuthorityUnavailable error instead of fabricating a local allocation -- it never mints or reuses an id on its own.

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": {
      "repo_root": "<repo_root>",
      "tenant_ref": "<tenant_ref>",
      "lane_ref": "<lane_ref>"
    },
    "name": "rm_concepts_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFor list: page size.
stateNoFor list: filter by claim state.
branchNoFor reserve, optional.
cursorNoFor list: opaque page cursor.
purposeNoFor reserve.
base_shaNoFor reserve, optional.
lane_refYesLane/worktree identity for fragment provenance.
candidateNoFor verify_candidate: a serialized Candidate contract payload.
namespaceNoFor reserve (required) or list (optional filter).
owner_refNoFor release/materialize (must match the claim owner).
repo_pathNoFor verify_candidate/verify_generation: the Git repository to diff.
repo_rootYesRepository working tree root.
candidatesNoFor verify_generation: serialized Candidate contract payloads.
concept_idNoFor reserve.
design_refNoFor reserve, optional.
generationNoFor verify_generation: a serialized Generation contract payload.
tenant_refYesAuthenticated tenant scope.
workitem_refNoFor reserve, optional.
run_trace_refNoFor reserve, optional.
concept_prefixNoFor list: filter by concept-id prefix.
expected_fenceNoFor release/materialize: the claim's current fence.
repository_refNoFor reserve.
reservation_idNoFor get/release/materialize.
provenance_refsNoFor reserve, optional.
request_key_refNoFor reserve: idempotency key.
source_tree_ishNoFor reconcile: the tree-ish to scan for markers.HEAD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare this is mutating, non-destructive, non-idempotent, and closed-world. The description adds valuable behavioral context beyond that: repository-manager never allocates ids locally and every mutating action refuses with named dependency_blocked/ConceptAuthorityUnavailable errors if the central authority is unavailable. It does not spell out exactly what reconcile mutates, but the dependency and failure-mode disclosure is substantial.

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

Conciseness4/5

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

The description is compact and front-loads the tool/domain context before explaining the authority dependency and refusal behavior. Its sentences are dense but not wasteful, though the first sentence spends space restating the name rather than defining the operation.

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?

For a 26-parameter tool with many action-specific parameters, the description is incomplete: it covers the central-authority dependency but omits what reconcile does, how to use the action-scoped parameters, and how this tool relates to the other rm_concepts siblings. The output schema and annotations reduce the burden, but the core operation remains undocumented.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema itself labels parameters by operation context (for list, for reserve, for release/materialize, for reconcile, etc.). The description adds no parameter-specific meaning beyond the authority behavior, so the baseline 3 is appropriate.

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

Purpose3/5

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

The description names the domain resource (concept-id claims) and the central authority it coordinates with, which is more than a bare restatement of the title. However, it never defines what the Reconcile operation actually does—e.g., scanning the tree-ish for markers and syncing claims—and it does not distinguish this tool from sibling concept operations such as reserve, list, or verify.

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 description explains failure behavior when the central authority is unavailable, but gives no guidance on when to choose this tool over sibling tools like rm_concepts_reserve, rm_concepts_list, or rm_concepts_verify_candidate. No prerequisites, alternatives, or when-not-to-use conditions 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