Skip to main content
Glama

get_task_status

Retrieve the status and progress of an asynchronous operation using its token. Returns completion state, errors, or redirect URI.

Instructions

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

The async tools (delete_entry, copy_entry, sometimes import_document) return an operation_token instead of the final result — call this to check whether the operation finished. For "wait until done" semantics, use wait_for_task instead so you don't have to write a polling loop.

Args: operation_token: The string token returned by the originating async tool.

Returns: Server's task payload — operationToken, operationType, percentComplete, status (one of NotStarted, InProgress, Completed, Failed, Canceled), redirectUri (set when the op produced a new entry, e.g. after a copy), entryId (the resulting entry's ID when applicable), errors (list — empty on success), and timestamps.

On failure: returns {"mode": "error", "error": <slug>, "operation_token": <str>, ...}. Common slugs: not_found (token unknown — usually expired or from a different server instance), auth_failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_tokenYesOperation token returned by an async tool (delete_entry, copy_entry, occasionally import_document). Server-scoped; tokens from a different server instance won't resolve.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, but description fully discloses behavior: returns detailed payload (operationToken, operationType, percentComplete, status, redirectUri, entryId, errors, timestamps) and error responses with common slugs (not_found, auth_failed).

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?

Well-structured: brief summary, then context, alternative tool, detailed Args and Returns. Every sentence adds value; no redundancy. Front-loaded with purpose.

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?

Given the tool's simplicity and presence of output schema, the description is comprehensive: covers purpose, usage, alternative, parameter semantics, and return values in detail, including errors.

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?

Input schema covers the only parameter (100% coverage). Description adds important context beyond schema: 'Server-scoped; tokens from a different server instance won't resolve,' which aids agent understanding.

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?

Clearly states the purpose: 'Look up the status of an async operation by its token.' Identifies the verb 'look up' and specific resource 'status of async operation,' and distinguishes from sibling tools like wait_for_task.

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?

Explicitly describes when to use: to check whether an async operation finished using an operation_token. Provides an alternative: 'For wait until done semantics, use wait_for_task instead so you don't have to write a polling loop.'

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/SamuelSHernandez/laserfiche-mcp'

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