Skip to main content
Glama
meilisearch

Meilisearch MCP Server

Official
by meilisearch

get-task

Retrieve detailed information about a specific task in Meilisearch by providing its unique task identifier (taskUid). Use this tool to monitor task progress and status updates.

Instructions

Get information about a specific task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskUidYes

Implementation Reference

  • Handler logic for the 'get-task' tool within the handle_call_tool function. Retrieves task information using the Meilisearch client and returns it as text content.
    elif name == "get-task":
        task = self.meili_client.tasks.get_task(arguments["taskUid"])
        return [
            types.TextContent(type="text", text=f"Task information: {task}")
        ]
  • Registration of the 'get-task' tool in the list_tools handler, including name, description, and input schema.
    types.Tool(
        name="get-task",
        description="Get information about a specific task",
        inputSchema={
            "type": "object",
            "properties": {"taskUid": {"type": "integer"}},
            "required": ["taskUid"],
            "additionalProperties": False,
        },
    ),
  • TaskManager.get_task helper method that wraps the Meilisearch client's get_task and serializes the result.
    def get_task(self, task_uid: int) -> Dict[str, Any]:
        """Get information about a specific task"""
        try:
            task = self.client.get_task(task_uid)
            return serialize_task_results(task)
        except Exception as e:
            raise Exception(f"Failed to get task: {str(e)}")
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets information', implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns structured data, or handles errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, clear sentence that is front-loaded with the core purpose. It avoids unnecessary words, making it efficient. However, it could be more structured by including key details, but as-is, it earns high marks for brevity.

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?

Given the tool's complexity (a read operation with one parameter), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover parameter meaning, return values, or behavioral traits, making it inadequate for the agent to use the tool effectively without additional context.

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?

The input schema has one parameter 'taskUid' with 0% description coverage, and the tool description adds no information about parameters. It doesn't explain what 'taskUid' represents, its format, or how to obtain it. With low schema coverage, the description fails to compensate, leaving the parameter undocumented.

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

Purpose2/5

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

The description 'Get information about a specific task' states the basic action but is vague about what information is retrieved. It distinguishes from siblings like 'get-tasks' (plural) by specifying 'specific task', but lacks detail on scope or content of the information. This is better than a tautology but remains general.

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 explicit guidance is provided on when to use this tool versus alternatives. The description implies usage for retrieving details of a single task, but it doesn't mention prerequisites, exclusions, or compare with siblings like 'get-tasks' (which likely lists multiple tasks) or 'cancel-tasks'. Without such context, the agent must infer usage from the name alone.

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

Related 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/meilisearch/meilisearch-mcp'

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