Skip to main content
Glama

Check Entry Staleness

check_entry_staleness
Idempotent

Detect whether a journal entry's anchors were modified or deleted in Git since the entry was created, so you can identify stale references before relying on them.

Instructions

Check if a journal entry's anchors have been modified or deleted in git since the entry was created.

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": "check_entry_staleness"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryIdNoThe ID of the journal entry to check (alias for entry_id)
entry_idNoThe ID of the journal entry to check
use_test_dbNo
workspaceIdNoWorkspace identifier alias
workspace_idNoWorkspace identifier (defaults to current project)
projectNumberNoNumeric project identifier alias
project_numberNoNumeric project identifier

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv9.1.0
    • changedInput schema / properties / entryId / description
      Previous value: -"The ID of the journal entry to check"New value: +"The ID of the journal entry to check (alias for entry_id)"
    • changedInput schema / properties / entryId / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
    • addedInput schema / properties / entry_id
      Added value: +{
      +  "description": "The ID of the journal entry to check",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / projectNumber
      Added value: +{
      +  "description": "Numeric project identifier alias",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / project_number
      Added value: +{
      +  "description": "Numeric project identifier",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace identifier alias",
      +  "type": "string"
      +}
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "Workspace identifier (defaults to current project)",
      +  "type": "string"
      +}
  2. First observedv9.0.0

TDQS

B3/5.0
Behavior1/5

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

The description frames the tool as a pure inspection ("Check if..."), but annotations declare readOnlyHint=false with idempotentHint=true, implying the call persists or updates staleness state. Nothing in the description discloses that side effect, what is written, or whether a previous verdict is cached — so an agent could reasonably treat this as a safe no-op read.

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?

A single front-loaded sentence with no filler; the resource and the staleness criterion come first. It is efficient, though the brevity leaves useful routing and effect information entirely unstated.

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?

An output schema exists, so return values need not be explained, and the schema covers most parameters. Still, for a 7-parameter tool with a non-read-only annotation and no required parameters, the description omits what git state it compares against, what happens when git history is unavailable, and that a mutation occurs.

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 86%, so the schema already explains entryId/entry_id, workspace and project identifiers. The description adds no meaning beyond that — no guidance on alias precedence, on when workspace_id or project_number are needed, or on the undocumented use_test_db flag.

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 ("check") and resource ("a journal entry's anchors") plus the criterion (modified or deleted in git since entry creation), so the operation is unambiguous. It does not distinguish itself from nearby siblings such as mark_anchors_stale or get_entry_history, which keeps it from a 5.

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?

Usage is only implied: you use it to find out whether an entry's code anchors have drifted. There is no explicit when/when-not guidance and no named alternative (e.g. mark_anchors_stale for actually flagging them, get_entry_history for entry revisions, get_commit_history for git-side inspection).

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