laserfiche-mcp

laserfiche_task_get_status

Check the status of an asynchronous Laserfiche operation using its operation token. Returns progress, completion state, entry ID, or error details to confirm whether the task succeeded.

Instructions

Look up the status of an async operation by its token.

Async tools (delete_entry, copy_entry, sometimes import_document) return an operation_token; call this to check progress, or wait_for_task for wait-until-done semantics.

Returns the server's task payload (status of NotStarted/InProgress/ Completed/Failed/Canceled, percentComplete, entryId when a new entry resulted, errors). On failure returns {"mode": "error", "error": <slug>} (not_found = token expired or wrong server).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operation_token`	Yes	Operation token returned by an async tool (delete_entry, copy_entry, sometimes import_document).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.3.0Sep 21, 2026

changedInput schema / properties / operation_token / description

Previous value: -"Operation token returned by an async tool (delete_entry, copy_entry, occasionally import_document). Server-scoped; tokens from a different server instance won't resolve."New value: +"Operation token returned by an async tool (delete_entry, copy_entry, sometimes import_document)."

removedInput schema / properties / operation_token / examples

Removed value: -[
-  "op-12345-abcd",
-  "task-9f2c-7c1e"
-]

First observedv2.1.0Jun 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and handles it excellently. It discloses the exact return payload fields, the error response shape, and the meaning of not_found (token expired or wrong server), giving the agent accurate expectations beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with the core purpose in the first sentence, followed by usage context and return details. Every sentence adds necessary information, and there is no redundancy or filler.

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?

For a single-parameter async status tool with a rich output schema, the description fully covers usage, alternatives, return payload, and error semantics. Nothing an agent needs to call and interpret this tool correctly is missing.

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?

The schema already documents operation_token fully, so the baseline is 3. The description adds value by explaining the token originates from async tools and that a not_found error indicates token expiry or wrong server, enriching the parameter's operational meaning.

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 the tool looks up status of an async operation by token, using a specific verb and resource. It also identifies the async tools that produce the token, distinguishing it from sibling tools like laserfiche_task_wait.

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 explains when to use this tool (check progress) versus the sibling wait_for_task tool (wait-until-done semantics). It also indicates which parent tools return operation_token, leaving no ambiguity about the appropriate calling context.

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