OriginGrid

Execute Batch

origingrid_execute_batch

Execute multiple search plan steps in batch. Accepts steps (array of step objects from origingrid_plan) and optional parallel_groups (array of arrays of step indices). Steps within the same parallel_group run concurrently on the server — the agent doesn't need to manage concurrency. Supports per-step timeout, automatic retry (default 1), and error isolation (one step failing doesn't affect others). Concurrency is limited to 8 by default for VPS memory safety. Returns structured results with elapsed timing per step. Combine with origingrid_plan: plan → execute_batch → agent reads the results. [ASRP: Call AFTER origingrid_plan. Steps in same parallel_group run concurrently.]

Input Schema

TableJSON Schema

Name	Required	Description
`steps`	Yes	Array of step objects (from origingrid_plan steps)
`retry_count`	No	Number of retry attempts per step
`step_timeout`	No	Per-step timeout in seconds
`batch_timeout`	No	Total batch timeout in seconds (max 90)
`parallel_groups`	No	Optional: groups of step indices to run in parallel. Each group waits for the previous to finish. Default: one step per group (serial).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`failed`	No
`results`	No
`completed`	No
`total_elapsed_ms`	No
`concurrency_limit`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations, the description fully discloses per-step timeout, automatic retry, error isolation, concurrency limit of 8, and returns structured results with timing.

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?

Well-front-loaded with core action, then details. Slightly long but every sentence is informative; could be tightened slightly.

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

Completeness4/5

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

Covers workflow with origingrid_plan, error handling, concurrency, timeouts. Minor gap: does not specify behavior if batch_timeout is exceeded (e.g., partial results).

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?

Schema covers 100% of parameters, but description adds significant meaning, especially for parallel_groups (concurrency behavior) and retry/timeout defaults.

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 it executes multiple search plan steps in batch, distinguishes from siblings by specifying it's used after origingrid_plan, and details the inputs and behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Call AFTER origingrid_plan' and explains concurrency management, but does not mention when NOT to use it (e.g., single step use origingrid_fetch).

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

All OriginGrid tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?