upservice-mcp

upservice_update_task

Idempotent

Update specific fields of a task without changing others. Provide only the task ID and the fields to modify, such as title, description, dates, or responsible employee.

Instructions

Partially update a task's fields (title, description, dates, responsible, etc).

Only fields you provide are changed; omitted fields are left unchanged.

Args: params (UpdateTaskInput): task_id (int) plus any fields to change, mentions (for description), and extra_fields for anything not explicitly modeled

Returns: str: JSON of the updated task record.

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": {
      "params": "<params>"
    },
    "name": "upservice_update_task"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations provide readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds value by explaining that only provided fields are changed and omitted ones remain unchanged, which goes beyond the annotations. No mention of side effects or authorization, but the annotations cover the non-destructive nature.

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

Conciseness5/5

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

The description is concise with a clear first sentence defining the action, followed by a brief explanation of partial update behavior. The Args and Returns sections are well-structured and not redundant. Every sentence adds value.

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

Completeness4/5

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

Given the tool's complexity (multiple optional fields, partial update) and the presence of a detailed schema and output schema, the description covers the essential behavior. It explains the update semantics and return format. Could optionally mention that date fields are ISO 8601, but that is already in the schema.

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?

Although context indicates 0% schema description coverage, the actual input schema provides detailed descriptions for each parameter. The description adds context for 'mentions' and 'extra_fields' beyond the schema, helping the agent understand their purpose. The listing of fields in the description is beneficial.

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 clearly states 'Partially update a task's fields' with a specific verb and resource. It lists example fields (title, description, dates, responsible, etc.) and distinguishes from sibling tools like create or delete tasks. The partial update behavior is explicitly emphasized.

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 explains the partial update behavior and lists updatable fields but does not explicitly state when to use this tool versus more specific siblings like upservice_update_task_status or upservice_update_task_estimation. Usage context is implied but not clearly delineated.

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

Deploy Server