upsprint-mcp

by Pedro-Roger

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Atribuir task (webhook)

assign_task

Assigns a task to a specific user by providing task ID and user ID.

Instructions

Atribui uma task a um usuário específico (action assignTask).

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": {
      "task_id": "<task_id>",
      "user_id": "<user_id>"
    },
    "name": "assign_task"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	UUID da task
`user_id`	Yes	UUID do usuário

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

C2.9/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. It only states the basic action without disclosing behavioral traits like idempotency, side effects, authorization needs, or what happens to previous assignments. The behavioral information is insufficient.

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, which is concise and contains the essential verb-resource pairing. It could be slightly expanded to add context without losing conciseness.

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?

For a simple two-parameter tool, the description is minimally sufficient but lacks details about the effect of assignment (e.g., overwriting) and any constraints. It does not leverage the opportunity to provide complete context.

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%, with each parameter described as UUID. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the action: assigns a task to a specific user. It includes the action name in parentheses for clarity. While it distinguishes from sibling tools (create, update, move), it does not explicitly contrast them, but the purpose is unambiguous.

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 vs alternatives. The description does not mention prerequisites, such as whether the task must exist or if the user must be valid, nor does it indicate if this assignment replaces prior assignments.

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

Deploy Server