agent-ops-mcp

Create task

create_task

Create a new task in the tracker by specifying a title and assignee, with optional priority and tags to organize work.

Instructions

Create a new task in the tracker.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "assignee": "<assignee>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Default
`tags`	No
`title`	Yes
`assignee`	Yes
`priority`	No	medium

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 23, 2026

TDQS

C2.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'create a new task,' which implies a mutation but does not disclose side effects, success/failure indicators, permissions required, or whether existing tasks are affected. The description is minimal and does not go beyond the obvious semantics of creation.

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

Conciseness2/5

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

The description is very concise (one sentence), but it is also under-specified. It sacrifices essential contextual information for brevity, resulting in an incomplete tool definition. The front-loading of 'create a new task' is clear, but the rest of the necessary details are absent, making the conciseness ineffective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations, no output schema, and 4 parameters with zero schema descriptions, the description must provide comprehensive guidance, but it does not. It omits required-field information, parameter semantics, return values, and any operational constraints. For a tool with this level of complexity, the description is severely inadequate, leaving an agent with insufficient information to call it correctly.

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

Parameters1/5

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

The input schema has 0% description coverage, so the description must compensate by explaining parameter meanings. However, the description does not mention any of the four parameters (title, assignee, priority, tags) or their required status. It provides no value in helping the agent understand what each parameter does or what values are expected, leaving the agent to rely solely on the schema's names and types.

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

Purpose4/5

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

The description states a clear verb ('create') and resource ('task in the tracker'), which distinguishes it from siblings like list_tasks and get_task. It is unambiguous that this tool creates a new task, but it does not elaborate on any unique capabilities or constraints beyond the basic action.

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, nor does it mention any prerequisites or exclusions. It only states what the tool does, leaving the agent to infer that creation is appropriate for new tasks without any context about how it relates to listing or retrieving tasks.

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

Deploy Server