Skip to main content
Glama
snussik
by snussik

check_batch_status

Monitor batch processing job status for OCR document extraction, enabling users to track progress and retrieve results from Mistral AI-powered text and table conversion operations.

Instructions

Check the status of a batch processing job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `check_batch_status` in `src/mcp_mistral_ocr_opt/main.py` implements the tool logic to check the status of a batch processing job using the `get_batch_processor` utility.
    @app.tool("check_batch_status")
    async def check_batch_status(arguments: Dict[str, Any]) -> List[TextContent]:
        """Check the status of a batch processing job."""
        job_id = arguments.get("job_id")
        if not job_id:
            raise McpError(ErrorData(code=INVALID_PARAMS, message="job_id is required"))
    
        try:
            batch_proc = await get_batch_processor()
            status = await batch_proc.get_job_status(job_id)
    
            return [
                TextContent(
                    type="text", text=json.dumps(status, indent=2, ensure_ascii=False)
                )
            ]
        except Exception as e:
            raise McpError(
                ErrorData(
                    code=INTERNAL_ERROR, message=f"Error checking batch status: {str(e)}"
                )
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure but only implies read-only safety through the verb 'check'. It omits rate limits, caching behavior, and error handling for invalid job IDs.

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 appropriately concise and front-loaded, but the overall description is undersized given the complexity of the opaque parameter structure and the tool's position in a multi-step workflow.

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?

Despite the presence of an output schema (reducing the need to describe return values), the description is incomplete as it fails to clarify the expected contents of the nested 'arguments' parameter and lacks lifecycle context for batch job management.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for the required 'arguments' object parameter. The description fails entirely to compensate by not explaining what specific fields (e.g., job_id) must be included in the generic arguments object.

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

Purpose4/5

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

The description clearly identifies the action (check status) and target resource (batch processing job). While minimal, it is not vague and maps directly to the tool name.

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 guidance is provided on when to use this versus siblings like list_batch_jobs (which may also return status) or download_batch_results, nor does it mention whether this is for polling or one-time checks.

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/snussik/mcp_mistral_ocr_opt'

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