Skip to main content
Glama

essay.project.unarchive

Restore a named module to the continue list after confirming the two-step unarchive action.

Instructions

Essay: essay.project.unarchive (Confirm two-step). Returns one module to the continue list. Name the module code.

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": {
      "module": "<module>"
    },
    "name": "essay.project.unarchive"
  }
}

Input Schema

NameRequiredDescriptionDefault
moduleYes
confirmPhaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; it does disclose that this is a state-changing operation and that a two-step confirmation applies, which is real information. However, it never explains how the confirmation works — whether the first call returns a token, what to pass as confirmPhase, or what happens on an unconfirmed call — leaving the mutation flow ambiguous.

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 text is short and front-loaded, but the fragmented telegraphic style ("Name the module code.") costs clarity without saving much space. Nothing is wasted, yet the terseness reads as under-specification rather than efficient compression.

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?

A confirmed two-step mutation with no annotations, no output schema, and 0% schema coverage needs a fuller description. As written, an agent cannot determine the confirmation protocol or the response of either phase, which is the central operational detail for this tool.

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% across 2 parameters, so the description is the only source of meaning. It clarifies that "module" is a module code (not an ID or display name), which is useful, but it says nothing about confirmPhase despite flagging a two-step confirm.

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 gives a specific verb-effect pair: it returns one module to the continue list, which is the inverse of the sibling essay.project.archive. The only weakness is that it never names that sibling, so the agent must infer the pairing from the shared name rather than from text.

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?

"Name the module code" gives invocation guidance and the tool name implies the archive/unarchive choice, but nothing explicitly states when to unarchive versus when to archive or re-stage a module. Usage is implied through naming convention rather than stated.

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