Skip to main content
Glama

latest_codex_sessions

Read-onlyIdempotent

Retrieve recent Codex CLI sessions to review past AI coding conversations and their outcomes. Set a limit to control how many sessions are returned.

Instructions

Return recent Codex sessions.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds almost nothing beyond that: it does not define the recency window, the ordering of results, whether the limit is applied before or after filtering, or what a returned session record contains. For a read tool with no output schema, that leaves meaningful behavioral gaps.

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 single sentence is efficient and front-loaded with no filler, which is good. But brevity here crosses into under-specification rather than genuine conciseness, since key facts about scope and the limit parameter are omitted entirely.

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?

With no output schema and zero parameter documentation, the description is the only place to learn what "recent" means, how results are ordered, and how the limit interacts with recency. None of that is present, leaving the definition inadequate for correct invocation even though the tool itself is simple.

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% for the single `limit` parameter, so the description carries the burden and fails to mention it at all. It does not explain that a maximum of 100 results applies, nor what the default of 10 means in practice relative to "recent". With only one parameter, a sentence on its meaning would have been cheap and valuable.

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

Purpose3/5

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

The description pairs a generic verb ("Return") with a specific resource ("recent Codex sessions"), so the broad intent is understandable. However, "recent" is undefined and nothing distinguishes this from siblings like get_codex_session, scan_codex_history, or search_codex_history. An agent cannot tell from this text whether it is a listing tool, a search, or a summary.

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?

There is no when-to-use guidance, no statement of when not to use it, and no reference to any alternative among the several Codex-related siblings. The agent must infer usage purely from the name.

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