MCP Node Tasks 05 - Sampling

Add task

add_task

Create a new task with a title and priority level to manage work items in the task list.

Instructions

Opretter en ny task i data/tasks.json

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>",
      "priority": "<priority>"
    },
    "name": "add_task"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Titlen på den nye task
`priority`	Yes	Prioritet: low, medium eller high

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose all behaviors. It mentions creating a task in a JSON file, which is basic, but lacks details on side effects, file persistence, or concurrency issues.

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 concise sentence, front-loaded with the key action. It is efficient, though could benefit from minor structural enhancements.

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

Completeness3/5

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

Given no output schema, the description does not explain return values or error states. For a simple create tool, it is minimally complete but lacks detail on success/failure behavior.

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 coverage is 100%, so the input schema already describes parameters adequately. The description adds no additional meaning beyond stating that a task is created.

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?

The description 'Creates a new task in data/tasks.json' clearly states the verb 'creates' and the resource 'task in data/tasks.json', distinguishing it from siblings like 'complete_task'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating tasks, but does not explicitly state when to use this tool versus alternatives or provide any exclusions. Sibling tool names offer some context but no direct guidance.

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

Deploy Server