Skip to main content
Glama

import_prior

Imports pre-install session logs as repository history for casebook backfill, preserving engineer instructions verbatim without creating threads, topics, decisions, or constraints.

Instructions

For the casebook backfill script only (thin client) — not for agents. Imports pre-install session logs as repository history: verbatim engineer instructions only, no threads, topics, decisions or constraints are created from them.

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": {
      "facts": "<facts>",
      "sessions": "<sessions>"
    },
    "name": "import_prior"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsYes
resetNo
sessionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the negative side effect — no threads, topics, decisions or constraints are created from imported instructions — which is real behavioral value. It says nothing about whether imports are idempotent, what `reset` destroys, or permission requirements.

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 dense sentence with the audience restriction front-loaded, which is the most important thing to read first. Slightly overpacked with a parenthetical and an em-dash, but nothing is wasted.

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?

Audience and side-effect scope are covered, but for a tool with nested-object parameters, no output schema, and no annotations, an agent lacks any description of the `reset` flag's consequences or what a successful import returns. Adequate for the stated script-only audience, thin as a standalone definition.

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% on 3 parameters, including a nested object (`facts`) and an array of free-form session items, so the description must compensate and largely does not. The phrase 'verbatim engineer instructions only' hints at what `facts`/`sessions` should contain, but `reset` and the shape of session entries are completely undocumented in both places.

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+resource: imports pre-install session logs as repository history, and implicitly scopes it away from the sibling read tools like search_prior by declaring it script-only. It falls short of 5 only because the operational outcome ('repository history') is left somewhat abstract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('For the casebook backfill script only') and explicit when-not ('not for agents'), which is exactly the routing signal an agent needs to back off. No named alternative is given, but the exclusion is decisive enough that an agent knows not to reach for it.

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