amazing-marvin-complete-mcp

set_priority

Idempotent

Instructions

Set priority (P1-P3 or low) or the dread level on a task. Set or change priority (isStarred) and/or the frog/dread level (isFrogged 1-4, read in the app 2026-10) on an existing TASK. Requires the Full Access Token. The app's four priority levels are stored as isStarred 3/2/1/-1; Low priority is shown only with 'Enable low priority' on. Does not apply to projects: they use the string field priority ('high'/'mid'/'low'); set it via update_category_or_project. A permanent 500 = the task does not exist (deleted or wrong ID).

Input Schema

TableJSON Schema

Name	Required	Description
`frog`	No	Dread/frog 1-4 (read in the app, 2026-10): 1=I dread this a little (A little), 2=I dread this (Dread), 3=I dread this a lot (A lot), 4=This might kill me (Toxic — requires 'Enable toxic frog level' in the account; Simple mode shows only one level). 0 removes (stored as false)
`item_id`	Yes	Task ID
`priority`	No	Priority (isStarred): 3=Most important/red, 2=Very important/orange, 1=Important/yellow, -1=Low priority (down arrow), 0=remove

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.7.3Oct 13, 2026

changedInput schema / properties / frog / anyOf

Previous value: -[
-  {
-    "maximum": 3,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 4,
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / frog / description

Previous value: -"Frog: 3=monster, 2=baby, 1=normal, 0=remove"New value: +"Dread/frog 1-4 (read in the app, 2026-10): 1=I dread this a little (A little), 2=I dread this (Dread), 3=I dread this a lot (A lot), 4=This might kill me (Toxic — requires 'Enable toxic frog level' in the account; Simple mode shows only one level). 0 removes (stored as false)"

Changed2 schema fields changedv1.4.0Aug 30, 2026

changedInput schema / properties / priority / anyOf

Previous value: -[
-  {
-    "maximum": 3,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 3,
+    "minimum": -1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / priority / description

Previous value: -"Priority: 3=red/highest, 2=orange, 1=yellow, 0=remove"New value: +"Priority (isStarred): 3=Most important/red, 2=Very important/orange, 1=Important/yellow, -1=Low priority (down arrow), 0=remove"

First observedv1.3.0Aug 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so safety is covered; the description goes well beyond by disclosing the Full Access Token requirement, the storage encoding (isStarred 3/2/1/-1), the account setting needed for Low/Toxic levels, and a concrete error contract (a permanent 500 means the task does not exist). This is exactly the extra context annotations cannot carry.

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?

Purpose is front-loaded in the first sentence, and the remaining sentences carry auth, encoding, account-setting, scope-exclusion and error information, all of which earn their place. There is mild redundancy (priority is defined once as P1-P3/low and again as isStarred values), which keeps it short of a 5.

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

Completeness5/5

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

An output schema exists, so return values need no explanation. With three simple parameters, full schema coverage, and annotations covering the mutation profile, the description supplies everything else an agent needs: auth prerequisite, scope limits, the removal sentinel, account settings affecting visibility, and the failure signature.

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?

Schema description coverage is 100%, so the baseline is 3; the description adds value by mapping the app-facing labels (P1-P3, low, dread levels 1-4) onto the integer encodings, including that 0 removes the setting. It is somewhat duplicative of the schema's own value documentation, keeping it just above baseline.

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?

States a specific verb (set/change) applied to a specific resource (priority and/or dread/frog level on a TASK), using the app's own vocabulary (P1-P3, low, isStarred, isFrogged). It explicitly distinguishes the target resource from projects, which use a different field and different sibling tool.

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

Usage Guidelines5/5

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

Names when the tool applies (existing TASK) and when it does not (projects), and routes the caller to the correct alternative by name: update_category_or_project for project priority. The 'existing task' constraint and the wrong-ID failure mode further bound correct usage.

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

Deploy Server