Skip to main content
Glama
Repository Manager

Repository Manager

Reserve

rm_concepts_reserve

Reserves concept IDs through the central authority and refuses mutations when that authority is unavailable, preventing local ID fabrication or reuse.

Instructions

Reserve (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_reserve"
  }
}

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.2/5.0
Behavior4/5

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

Beyond the annotations, the description adds important behavioral context: repository-manager never allocates concept ids locally, and mutating actions fail with dependency_blocked/ConceptAuthorityUnavailable when the central authority is unavailable. It does not fully describe reservation exclusivity, ownership, or conflict behavior, but it substantially supplements the safety annotations.

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 reasonably front-loaded with the tool name and core purpose, but it is dense with implementation jargon such as injected authority port and RMDD-16. The second paragraph is a long sentence that mixes several behavioral points without structuring the multi-action surface.

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 whose schema references list, release, materialize, verify_candidate, verify_generation, and reconcile operations, the description covers only the reserve/authority behavior. It leaves the broader action surface unexplained, so an agent cannot infer the full invocation model from the description alone.

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 schema already documents all 26 parameters. The description adds no parameter-level meaning, which is acceptable at baseline 3 when the schema does the heavy lifting.

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 clearly states a specific verb and resource: reserving/coordinating concept-id claims against a central authority. It is understandable apart from generic repository tools, but it does not explicitly distinguish itself from sibling concept tools such as rm_concepts_list, rm_concepts_get, or rm_concepts_release.

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 the authority dependency and failure behavior, but it gives no guidance on when an agent should call this tool versus the many sibling concept tools. It also does not explain how to select among the reserve/list/get/release/materialize/verify actions implied by the schema.

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