Skip to main content
Glama

repo_publish_memory

Idempotent

Publishes a locally approved memory as a Git-versioned team memory file for review and commit.

Instructions

Publish a locally approved memory as a Git-versioned team memory file for review and commit.

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": {
      "id": "<id>"
    },
    "name": "repo_publish_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent, non-open-world write, so the safety profile is covered. The description adds that the output is a Git-versioned file routed for review and commit, which is useful context, but it doesn't say whether an existing file is overwritten, where the file lands, or what happens on publish of an unapproved id.

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?

One front-loaded sentence with no filler; the action and artifact come first. Slightly terse given the lifecycle context it is compressing into a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Annotations carry the safety profile and there is no output schema to explain, so the remaining burden is small. Still, for a lifecycle-mutating step, the definition leaves the prerequisite state, the 'id' meaning, and the publish result underspecified.

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

Parameters2/5

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

Schema description coverage is 0% and the single 'id' parameter is documented nowhere. The description never clarifies whether 'id' refers to a memory identifier, and with no other params to infer from, it must compensate and does not.

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?

States a specific verb ('Publish') and resource (a locally approved memory) plus the resulting artifact ('Git-versioned team memory file'). The 'locally approved' qualifier distinguishes it from sibling stages like repo_stage_memory and repo_approve_memory, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Locally approved' implies a prerequisite state (approval must have happened first), which is real usage guidance. However, it never explicitly says when to call this instead of repo_stage_memory or repo_approve_memory, nor what to do if the memory is not yet approved.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.