Skip to main content
Glama

search_prior

Find the exact words an engineer typed in sessions before Worktrail was installed. Use it to recall old requests or past activity, not recorded decisions or evidence.

Instructions

Search what the engineer actually typed in sessions from BEFORE casebook was installed (repository history, imported by backfill). Returns their words verbatim with the source session — never a conclusion, and never anything an agent said. Nothing here is a decision or a constraint: it is raw material, and it may describe approaches that were later abandoned. Use it when the engineer asks what they were doing back then, or when you need the original wording of an old request; use search_evidence for recorded work.

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": {
      "query": "<query>"
    },
    "name": "search_prior"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return content (verbatim words plus source session), the exclusions (never a conclusion, never anything an agent said), and the epistemic caveat that results are raw material that may describe abandoned approaches. It leaves out pagination/ordering behavior around limit and does not explicitly state the operation is a read, which is only implied by 'search'.

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?

Front-loaded with the scope-defining sentence, and each following sentence adds a distinct constraint. The triple negation ('never a conclusion', 'never anything an agent said', 'nothing here is a decision or a constraint') is slightly redundant emphasis, but the content is dense and worth keeping.

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?

No output schema exists, so the description must describe returns, and it does so concretely (verbatim words with source session). For a two-parameter read tool with no annotations, the remaining gap is the undocumented limit behavior and result ordering, which is minor but real.

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 must compensate. It does clarify the corpus that query runs against (pre-install session utterances, not recorded evidence), which meaningfully shapes how an agent should phrase a query, but it says nothing about matching semantics or about the limit parameter's default of 10 and its maximum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) plus the exact resource and its scope: what the engineer typed in sessions from BEFORE casebook was installed, imported by backfill. It also explicitly contrasts with search_evidence ('use search_evidence for recorded work'), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

Gives two concrete triggering conditions ('when the engineer asks what they were doing back then' and 'when you need the original wording of an old request') and names the alternative tool with the condition that selects it. No inference required.

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