Skip to main content
Glama

elenchus_start_session

Initiate a new code verification session by collecting initial context, building a dependency graph, and setting up the mediator for adversarial analysis.

Instructions

Start a new Elenchus verification session. Collects initial context, builds dependency graph, and initializes mediator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget path to verify (file or directory)
requirementsYesUser verification requirements
workingDirYesWorking directory for relative paths
maxRoundsNoMaximum rounds before forced stop
verificationModeNoVerification mode configuration for controlling convergence behavior. Use "fast-track" or "single-pass" for one-shot verification.
differentialConfigNoDifferential analysis configuration. When enabled, only verifies code that has changed since the last verification baseline.
cacheConfigNoResponse caching configuration. When enabled, caches verification results to skip re-verification of unchanged files.
chunkingConfigNoSelective context configuration. When enabled, chunks files into function-level pieces for more efficient verification.
pipelineConfigNoTiered pipeline configuration. When enabled, uses screen→focused→exhaustive verification tiers with auto-escalation.
safeguardsConfigNoQuality safeguards configuration. Ensures verification quality when using optimizations (caching, chunking, tiered).
dynamicRoleConfigNoDynamic role generation configuration. When enabled, generates customized Verifier/Critic roles based on requirements using LLM.
llmEvalConfigNoLLM-based evaluation configuration. When enabled, uses LLM reasoning for convergence, severity, edge case, and false positive evaluation.
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions what the tool does internally but does not disclose side effects like state changes, resource locking, authentication needs, or error conditions. For a session-starting tool, more behavioral context is needed.

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?

The description is short (1 sentence plus two fragments) and front-loaded with the core action. It is not verbose but could be slightly restructured for clarity. Overall, efficient but missing some organizational structure.

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?

Given the complexity (12 parameters, many nested objects), the description is too sparse. It does not explain the relationship between the many configuration options or what the session returns. No output schema, so return values are undocumented. A more complete summary of available configurations is warranted.

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 coverage is 100%, so each parameter has a description. The tool-level description adds a high-level purpose ('collects initial context, builds dependency graph') but does not explain individual parameters beyond the schema. Baseline is 3; description does not significantly enhance meaning.

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?

The description clearly states the tool starts a new Elenchus verification session, with specific actions (collect context, build dependency graph, initialize mediator). It uses a strong verb-resource pair 'Start a new Elenchus verification session' and distinguishes itself from sibling tools like end_session or start_reverification.

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?

No explicit guidance on when to use this tool versus alternatives. While it implies it is the first step in a verification workflow, it does not specify prerequisites, conditions, or mention when not to use it (e.g., if a session already exists).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jhlee0409/elenchus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server