Skip to main content
Glama
Repository Manager

Repository Manager

Materialize

rm_concepts_materialize

Materializes a concept claim by coordinating its concept ID with the central authority, refusing to allocate or reuse IDs when that authority is unavailable.

Instructions

Materialize (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_materialize"
  }
}

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

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) by disclosing that the tool is a pure consumer of an injected authority port, never mints or reuses an id locally, and fails with a named dependency_blocked/ConceptAuthorityUnavailable error when that authority is absent. That failure-mode and non-fabrication guarantee is exactly the kind of behavioral context annotations can't express, though auth/rate-limit and partial-failure behavior remain unstated.

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 lead line is a name restatement in parentheses before any useful content, and the following paragraph is generic architecture prose that applies to every rm_concepts mutation rather than this operation. Readable and not bloated, but it front-loads trivia instead of the tool's action.

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 multiplexed surface with no action discriminator, an agent needs the description to explain which parameter subset applies to materialize and what the operation returns; instead it covers only the authority-port dependency. The existence of an output schema covers return values, but the operation semantics gap is significant at this complexity.

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 every one of the 26 parameters is already documented in the schema (including action-specific notes like "For release/materialize: the claim's current fence"). The description adds no parameter-level meaning at all, so the baseline 3 applies.

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?

"Materialize (rm_concepts)" essentially restates the tool name and title; the body explains the family's authority-port architecture but never says what materializing a concept actually does (presumably promoting a reservation into a materialized concept artifact). Against siblings like rm_concepts_reserve, _release, _verify_candidate and _reconcile, an agent gets the domain but no differentiating verb semantics.

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?

No statement of when to choose materialize over rm_concepts_reserve, _release, or _get. The only usable cue is the precondition that the RMDD-16 central authority must be available, which is a runtime condition rather than routing 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