Skip to main content
Glama
mokafari

MCP Orchestrator Server

by mokafari
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

get_task_status

Check the status of all tasks in the orchestration system to monitor progress and coordinate workflows.

Instructions

Get status of all tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:297-305 (handler)
    Handler implementation for the 'get_task_status' tool. It returns a JSON string containing the status of all tasks.
    case "get_task_status": {
  debug('Getting task status');
  return {
    content: [{
      type: "text",
      text: JSON.stringify(Object.values(tasks), null, 2)
    }]
  };
}
  • src/index.ts:438-446 (registration)
    Registration of the 'get_task_status' tool in the ListTools response, including its name, description, and empty input schema.
    {
  name: "get_task_status",
  description: "Get status of all tasks",
  inputSchema: {
    type: "object",
    properties: {},
    required: []
  }
},

Tool Definition Quality

C2.8/5.0
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 for behavioral disclosure. 'Get status of all tasks' implies a read-only operation that returns status information, but it doesn't specify what 'status' entails (e.g., pending, completed, error states), whether it includes metadata or just state, or if there are limitations like pagination or rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence: 'Get status of all tasks'. It's front-loaded and wastes no words, making it easy to parse. However, it could be slightly more specific (e.g., 'Retrieve the current status for all tasks in the system') to enhance clarity without losing 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 the complexity of task management (with siblings for creation, completion, deletion, and other get operations), the description is incomplete. No annotations exist to clarify behavior, and there's no output schema to describe return values. The description doesn't explain what 'status' includes or how it differs from other get tools, leaving the agent with insufficient context for effective use.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't mention any parameters, which is appropriate since none exist. It adds no semantic value beyond the schema, but with zero parameters, the baseline is 4 as there's nothing to compensate for.

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 status of all tasks' clearly states the verb ('Get') and resource ('status of all tasks'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'get_task_details' or 'get_next_task', leaving ambiguity about what specific status information is provided versus other get operations.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_task_details' (likely for individual tasks) and 'get_next_task' (likely for queued tasks), there's no indication whether this tool returns aggregated statuses, summary information, or a list of all tasks without filtering. No explicit when/when-not or alternative recommendations are included.

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/mokafari/orchestrator-server'

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