Iterator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_datasetC | Load a dataset file for processing (supports JSON Lines format) |
| load_json_datasetA | Load a JSON dataset using a jq expression that returns an array of records |
| get_next_recordC | Get the next record from the dataset for processing |
| save_resultB | Save the processing result for the current record |
| export_resultsB | Export all processing results to a file |
| get_statusB | Get current processing status and progress |
| reset_to_startA | Reset the iterator to the beginning of the dataset |
| jump_to_recordB | Jump to a specific record number in the dataset |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Dataset Status | Information about the currently loaded dataset |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: loading datasets (two separate tools for different formats), navigating records (next, jump, reset), obtaining status, and saving/exporting results. No overlaps or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case, using appropriate verbs like get, load, save, export, jump, and reset. The naming convention is uniform and predictable.
With 8 tools, the server covers the essential operations for an iterator: dataset loading, record navigation, processing, status tracking, and result export. The count is balanced—neither sparse nor bloated.
The tool set covers the full lifecycle of iterative processing: loading data (including a variant for jq expressions), navigating (next, jump, reset), saving per-record results, and exporting all results. Missing features like batch operations or record deletion are minor gaps given the server's focused scope.