Skip to main content
Glama

scan_codex_history

Idempotent

Scans local Codex session files into the local search index so you can find and reuse past CLI history.

Instructions

Scan local Codex session files into the local search index.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already state readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description correctly adds that the scan is local and writes into a search index, consistent with the non-read-only, idempotent profile. It does not say whether indexing is full or incremental, how expensive or long the scan is, or what happens to stale index entries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler. Every word, including 'local' and 'search index', carries meaning, so I can find no reasonable way to trim it.

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?

With no output schema, the description should say what a scan returns or confirms, such as counts, the affected index, or whether a re-scan is required after new sessions. For a zero-parameter, idempotent indexing operation, it is serviceable but leaves the agent guessing about results and side effects.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema is self-explanatory. The baseline for a zero-parameter tool applies, and nothing in the text misleads about inputs.

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 has a specific verb and resource: 'Scan local Codex session files into the local search index.' It makes clear that the tool ingests local session data and writes it into a search index, which distinguishes it from search_codex_history. It does not explicitly name that sibling as an alternative, so it is not 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?

There is no explicit when-to-use, when-not-to-use, or prerequisite guidance. Usage is only implied: the phrase 'into the local search index' suggests this tool populates the index that search_codex_history later reads. An agent must infer this rather than read it.

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