Skip to main content
Glama

sequential_search

Read-only

Track multi-step research progress with persistent sessions, branching, and knowledge gap tracking to organize your research workflow.

Instructions

Track multi-step research progress with persistent sessions, branching, and knowledge gap tracking. This is a state tracker, not a search tool — pair with web_search or search_and_scrape for actual searches. Call with stepNumber=1 (omit sessionId) to start a new session. Returns JSON with fields: sessionId, currentStep, totalStepsEstimate, isComplete, steps (array of {stepNumber, description, isRevision, revisesStep, branchId, timestamp}), sources, gaps (array of {description, foundInStep}), startedAt, completedAt (only when isComplete=true). Pass sessionId for steps 2+; each call returns the full accumulated session state. Set nextStepNeeded=false on final step to mark complete. Sessions expire after 30 min of inactivity (returns 'session expired or not found' error); max 50 concurrent sessions per tenant. Use branchFromStep + branchId to explore alternative directions without losing the main thread. Not cached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchStepYesSummary of what was researched or discovered in this step. Be descriptive to build a useful research trail.,required
stepNumberYesCurrent step number (start at 1 for a new session). Must increment sequentially.,required
nextStepNeededYesSet true if more research steps will follow; false to mark the session complete.,required
totalStepsEstimateNoYour estimate of total steps needed. Update as scope becomes clearer.
sessionIdNoSession ID returned from the first call. Required for steps 2+. Omit to start a new session.
isRevisionNoSet true if this step revises a previous step's findings.
revisesStepNoThe step number being revised (required if isRevision is true).
branchFromStepNoStep number to branch from, for exploring alternative research directions.
branchIdNoIdentifier for this research branch (e.g. 'technical-approach' vs 'business-angle').
knowledgeGapNoA specific gap or unanswered question identified during this step that needs further investigation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
completedAtNo
currentStepNo
gapsNo
isCompleteNo
sessionIdNo
sourcesNo
startedAtNo
stepsNo
totalStepsEstimateNo
Behavior1/5

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

The description implies write operations (starting sessions, updating state) but annotations set readOnlyHint=true, creating a direct contradiction. This misalignment severely undermines transparency for an AI agent selecting the tool.

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?

At ~150 words, the description is reasonably concise given the complexity. It front-loads the key purpose and pairing advice, and each sentence adds value (session lifecycle, branching, limits). Minor redundancy could be trimmed, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, output schema, sibling tools), the description covers purpose, usage, return format, session lifecycle, concurrency limits, expiration, branching, and caching. Output schema presence is noted and described. Comprehensive for a state tracker.

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 baseline is 3. The description adds usage context (e.g., how to start/continue sessions, branching), but individual parameter meanings are already clear from schema descriptions. No significant additional semantics beyond orchestration guidance.

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 identifies the tool as a 'state tracker, not a search tool' and contrasts it with sibling tools like web_search and search_and_scrape. The verb 'Track' and resource 'multi-step research progress' are specific, making it easy to distinguish.

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?

The description explicitly states when to use this tool (for tracking research progress) and when not to (for actual searches), directing the agent to pair with search tools. It provides clear step-by-step instructions for starting a session (stepNumber=1, omit sessionId) and continuing (pass sessionId).

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/zoharbabin/web-researcher-mcp'

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