Skip to main content
Glama
Repository Manager

Repository Manager

Release

rm_concepts_release

Release concept-id claims through the central authority, refusing mutations when that authority is unavailable so IDs are never minted or reused locally.

Instructions

Release (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_release"
  }
}

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

C2.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds meaningful behavioral context beyond annotations: a central authority dependency, refusal with named dependency_blocked/ConceptAuthorityUnavailable errors, and a guarantee that the tool never mints or reuses an id locally. It does not describe release-specific effects, but the external-dependency and refusal semantics are valuable.

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

Conciseness2/5

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

The description is not front-loaded with release's action; it begins with the title and then spends most of its length on the architecture shared by all concept tools. The dependency paragraph is useful but unfocused for a single release operation, so the structure does not help an agent quickly identify what this tool does.

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?

This is a complex tool with 26 parameters (many marked 'For list', 'For reserve', etc.) and an output schema. The description explains the authority dependency and refusal behavior, but it omits which parameters actually apply to release and what release changes, leaving the agent to infer release semantics from scattered schema notes.

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%, so the baseline is 3 even without parameter details in the description. The description adds no release-specific parameter meaning—such as the roles of reservation_id, owner_ref, or expected_fence—and relies entirely on the schema's per-parameter 'For release/materialize' notes.

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

Purpose2/5

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

The description opens with the title 'Release' and a broad statement about concept-id claim coordination, but never says what release actually does—whether it releases a reservation/claim, what entity is affected, or what successful outcome means. It also describes all rm_concepts actions collectively, so it does not distinguish this tool from rm_concepts_reserve, rm_concepts_materialize, rm_concepts_reconcile, etc.

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?

There is no when-to-use guidance or named alternative for release versus the other rm_concepts actions. The only condition given is that mutating actions refuse when the central authority is unavailable, which is a failure-mode note rather than usage guidance.

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