Skip to main content
Glama
snussik
by snussik

list_batch_jobs

Retrieve and filter batch OCR processing jobs from the Mistral AI document extraction server to monitor and manage document conversion operations.

Instructions

List batch jobs with optional filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `list_batch_jobs` tool handler, which uses the batch processor to fetch jobs and returns them as a JSON-formatted list.
    @app.tool("list_batch_jobs")
    async def list_batch_jobs(arguments: Dict[str, Any]) -> List[TextContent]:
        """List batch jobs with optional filtering."""
        try:
            batch_proc = await get_batch_processor()
            jobs = await batch_proc.list_jobs(
                status=arguments.get("status"),
            )
    
            return [
                TextContent(
                    type="text",
                    text=json.dumps({"jobs": jobs}, indent=2, ensure_ascii=False),
                )
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but only minimally delivers. It notes 'optional filtering' but fails to clarify what filters are supported, whether results are paginated, or the scope of data returned (e.g., all jobs vs. user's jobs).

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?

Extremely terse at six words. While efficient and front-loaded, the brevity is inappropriate given the schema complexity—leaving critical gaps rather than being appropriately concise. No structural issues, but under-specified.

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?

Incomplete given the tool's complexity. The arbitrary 'arguments' object (allowing any properties) desperately requires documentation of valid filter fields, which is absent. While output schema exists (reducing need to describe return values), the input contract is essentially undocumented.

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

Parameters2/5

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

Schema coverage is 0% and the single parameter 'arguments' is an opaque object with 'additionalProperties: true' (accepts arbitrary keys). Description mentions 'optional filtering' which weakly maps to the parameter's purpose, but provides no valid keys, value types, or examples to compensate for the completely undocumented schema.

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?

States specific verb 'List' and resource 'batch jobs', giving a clear high-level purpose. However, fails to distinguish from sibling tool 'check_batch_status' which could confuse agents about whether this returns status details or just job references.

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?

Provides no guidance on when to use this versus siblings like 'check_batch_status' or after 'create_batch_job'. Does not mention prerequisites (e.g., whether jobs must exist first) or pagination behavior despite being a list operation.

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