Skip to main content
Glama
Repository Manager

Repository Manager

Get

rm_concepts_get
Read-onlyIdempotent

Retrieves concept-ID claim details from the central authority to coordinate repository reservations without creating local IDs.

Instructions

Get (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_get"
  }
}

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only family-level context about the injected authority port and its dependency_blocked error, but says nothing about Get's own behavior — e.g., whether reads also require the authority, what happens for an unknown reservation_id, or whether results are cached. It does not contradict the annotations, but for a read tool it emphasizes mutation semantics that do not apply.

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?

Three sentences of implementation detail (backticked module paths like scion_sdk.governance.concept_reservation) occupy the prime front-loaded position, while the operative fact — what Get returns — is absent. Content that does not help an agent call Get is spending the description's limited budget.

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?

With 26 parameters, an output schema, and no annotations gap on safety, the description's job is to orient the agent to the read path and disambiguate from the six sibling concept tools. It fails on both: an agent still cannot tell what Get returns, which parameter drives it, or when to prefer rm_concepts_list. Output schema presence excuses return-value detail, but not the missing selection guidance.

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 all 26 parameters carry 'For list:/For reserve:/For get...' usage notes, so the schema already does the heavy lifting. The description adds no parameter guidance at all — notably nothing clarifying that reservation_id is the operative input for Get and that the other 24 fields are irrelevant — so it merits only the baseline.

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 restates the name ("Get (rm_concepts)") and then discusses the concept-id authority architecture rather than what this specific tool returns or does. It never says Get retrieves a reservation/claim by reservation_id, nor how it differs from rm_concepts_list or rm_concepts_reserve. The text is closer to tautology plus architectural context than a statement of purpose.

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 and no alternatives named, despite seven rm_concepts_* siblings. Worse, it frames the tool around 'every mutating action refuses', which is irrelevant or misleading for a read-only Get and gives no signal about when an agent should call it instead of list.

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