Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-task

Retrieve detailed status and progress information for a specific Meilisearch task using its unique identifier to monitor indexing or operation completion.

Instructions

Get information about a specific task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskUidYesUnique identifier of the task

Implementation Reference

  • The handler function that implements the core logic of the 'get-task' tool. It makes an API call to retrieve details of the specified task and returns the result as formatted JSON or an error response.
    async ({ taskUid }: GetTaskParams) => {
      try {
        const response = await apiClient.get(`/tasks/${taskUid}`);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod schema for validating the input parameters of the 'get-task' tool, specifically requiring a 'taskUid' number.
    {
      taskUid: z.number().describe("Unique identifier of the task"),
    },
  • TypeScript interface defining the expected parameters for the 'get-task' tool handler.
    interface GetTaskParams {
      taskUid: number;
    }
  • The registration of the 'get-task' tool using server.tool(), including name, description, input schema, and handler function.
    server.tool(
      "get-task",
      "Get information about a specific task",
      {
        taskUid: z.number().describe("Unique identifier of the task"),
      },
      async ({ taskUid }: GetTaskParams) => {
        try {
          const response = await apiClient.get(`/tasks/${taskUid}`);
          return {
            content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:70-70 (registration)
    Top-level call to register the task tools module, which includes the 'get-task' tool.
    registerTaskTools(server);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get information' but doesn't disclose behavioral traits such as whether it's read-only (implied by 'get'), error handling (e.g., if taskUid is invalid), response format, or any rate limits. The description is minimal and misses key operational details.

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 sentence ('Get information about a specific task'), which is appropriately sized and front-loaded with the core purpose. There's no wasted text, but it could be more informative without sacrificing conciseness.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what information is returned, error conditions, or how it fits with siblings like 'get-tasks'. For a tool with one parameter, it's minimal but lacks necessary context for effective use.

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

Parameters3/5

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

Schema description coverage is 100% (taskUid is documented as 'Unique identifier of the task'), so the baseline is 3. The description adds no meaning beyond the schema—it doesn't explain parameter constraints, format, or examples. It relies entirely on the schema for parameter documentation.

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

Purpose3/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' clearly states the verb ('Get') and resource ('task'), but it's vague about what information is retrieved. It distinguishes from siblings like 'get-tasks' (plural) by specifying 'specific task', but doesn't clarify how it differs from 'list-tasks' or 'wait-for-task' in terms of scope or detail.

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 tool versus alternatives. It doesn't mention prerequisites (e.g., needing a taskUid), exclusions, or comparisons to siblings like 'get-tasks' (for multiple tasks) or 'wait-for-task' (for blocking until completion). The description implies usage for a single task but lacks explicit context.

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/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

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