Skip to main content
Glama

Restore Entry

restore_entry

Restore a soft-deleted journal entry by supplying its entry ID, workspace ID, and project number to recover the entry.

Instructions

Restore a soft-deleted journal entry.

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

Input Schema

NameRequiredDescriptionDefault
entry_idNo
workspace_idNo
project_numberNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
detailsNoAdditional error context
entryIdNo
successNo
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. Changed2 schema fields changedv9.1.0
    • addedInput schema / properties / project_number
      Added value: +{
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv9.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower; the description's only added behavior is that restoration applies to soft-deleted entries. It omits what happens if the entry is not deleted, whether the restore is reversible, and permission/scope requirements.

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?

A single front-loaded sentence with no filler, but its brevity comes from under-specification rather than economy — the same length could have covered the required scope or the discoverability path.

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?

An output schema exists so return values need no explanation, but for a mutation tool with three undocumented parameters, the description leaves out how to locate a deleted entry, which workspace context applies, and what state the entry lands in after restore.

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

Parameters1/5

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

Schema description coverage is 0% and the description says nothing about entry_id, workspace_id, or project_number — including why all three are optional (required: []). With three undocumented parameters and no compensating text, an agent must guess what to supply and how workspace_id and project_number interact with entry_id.

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?

"Restore a soft-deleted journal entry" gives a specific verb (restore) and resource (journal entry) with the key qualifier that the target must already be soft-deleted. It does not distinguish itself from the near-identical sibling team_restore_entry, so an agent cannot tell which variant to call from the description alone.

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?

No when-to-use guidance, no prerequisites (e.g. that the entry must first be soft-deleted), and no pointer to list_deleted_entries / team_list_deleted_entries for discovering restorable entries. The only usage hint is implicit in the phrase "soft-deleted".

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