Skip to main content
Glama

repo_reject_memory

DestructiveIdempotent

Reject a staged repository memory by ID, with an optional note, to prevent unapproved context from being committed and keep agent memory accurate.

Instructions

Reject a staged repository memory.

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_reject_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds nothing about what rejection actually does to the staged memory (deleted permanently, archived, or returned to draft) or whether a reason is recorded, which matters for a destructive mutation.

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 single sentence is front-loaded and contains no filler, but its brevity comes from under-specification rather than efficiency. It earns its words but does not use enough of them.

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 destructive mutation with no output schema and zero parameter documentation, the description should explain the effect on the staged memory and the role of the note field. None of that is present, leaving the agent to guess at consequences.

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% across two parameters, so the burden is on the description and it says nothing about them. 'id' is inferable as the memory identifier, but 'note' (presumably a rejection reason) is completely undefined in both schema and description.

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 pairs a specific verb ('Reject') with a specific resource ('staged repository memory'), so an agent can tell it acts on staged memories rather than published ones. It does not explicitly contrast itself with the sibling repo_approve_memory, but the action is unambiguous.

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 guidance on when to reject versus approve, no mention of the staging/review workflow this belongs to, and no prerequisites such as required permissions. The agent must infer from the sibling name repo_approve_memory that this is the negative branch.

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