Skip to main content
Glama

Mark Anchors Stale

mark_anchors_stale
Idempotent

Update multiple anchors to stale or invalidated when validation rules or Git history checks show they no longer apply, keeping project memory accurate.

Instructions

Update the status of multiple anchors (e.g. to stale or invalidated) based on validation rules or git history checks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mark_anchors_stale"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesNo
use_test_dbNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
successYes
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
updated_countYes
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv9.1.0
    • changedInput schema / properties / updates / items / properties / id / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / updates / items / properties / status / enum
      Removed value: -[
      -  "pending",
      -  "valid",
      -  "stale",
      -  "invalidated",
      -  "unresolvable"
      -]
  2. First observedv9.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context by naming the statuses it writes ('stale or invalidated') and the basis for the change, but it says nothing about what happens to anchor IDs that don't exist, whether the update can be reverted, or how the status interacts with search/validation later. With annotations carrying the mutation semantics, a 3 is appropriate.

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 that names the action, the resource, and the example outcomes with no filler. It could be slightly longer only to add the missing usage and parameter detail, not because the current text is bloated.

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

Completeness4/5

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

An output schema exists, so return-value explanation is not required, and the annotations cover safety and idempotency. What remains thin is the mismatch between the tool name (mark stale) and the broader description (any status, e.g. invalidated), plus the undocumented test-database flag; these are real but modest gaps for a two-parameter batch mutation.

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 0%, so the description carries the burden. It partially compensates: 'multiple anchors' explains the batch shape of the updates array and 'e.g. to stale or invalidated' supplies example status values that the schema lacks entirely (no enum). However, the use_test_db parameter is never mentioned, nor is the accepted format of the anchor id, leaving half the surface undocumented.

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 and resource: 'Update the status of multiple anchors', with example target statuses (stale, invalidated) and the basis for the change (validation rules or git history). It does not distinguish itself from the nearby sibling check_entry_staleness, which appears to be the read-side counterpart, so sibling differentiation is left implicit.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative. The phrase 'based on validation rules or git history checks' hints at the triggering context but does not tell the agent when to prefer this tool over check_entry_staleness or a manual status update via batch_update_entries.

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