Amazing Marvin MCP

by bgheneti

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_currently_tracked_item

Retrieve the currently tracked task or project from Amazing Marvin to see your active focus.

Instructions

Get currently tracked item from Amazing Marvin

Input Schema

TableJSON Schema

Name	Required	Description	Default
`debug`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`metadata`	Yes	Metadata about the data itself
`summary`	Yes	Human-readable insights
`debug`	Yes
`success`	Yes
`api_version`	No		current
`response_version`	No		1.0

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv0.1.7May 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedOutput schema / $defs

Removed value: -{
-  "ErrorDetails": {
-    "properties": {
-      "error_type": {
-        "type": "string"
-      },
-      "message": {
-        "type": "string"
-      },
-      "retry_suggested": {
-        "default": false,
-        "type": "boolean"
-      },
-      "user_message": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "error_type",
-      "message",
-      "user_message"
-    ],
-    "type": "object"
-  },
-  "ResponseDebug": {
-    "properties": {
-      "api_calls_made": {
-        "default": 1,
-        "type": "integer"
-      },
-      "api_endpoint": {
-        "type": "string"
-      },
-      "cache_hit": {
-        "default": false,
-        "type": "boolean"
-      },
-      "error": {
-        "anyOf": [
-          {
-            "$ref": "#/$defs/ErrorDetails"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      },
-      "response_time_ms": {
-        "type": "integer"
-      },
-      "warnings": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      }
-    },
-    "required": [
-      "api_endpoint",
-      "response_time_ms"
-    ],
-    "type": "object"
-  },
-  "ResponseMetadata": {
-    "properties": {
-      "count": {
-        "type": "integer"
-      },
-      "data_freshness": {
-        "default": "real_time",
-        "type": "string"
-      },
-      "end_date": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      },
-      "filters_applied": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      },
-      "source": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      },
-      "start_date": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      }
-    },
-    "required": [
-      "count"
-    ],
-    "type": "object"
-  },
-  "ResponseSummary": {
-    "properties": {
-      "action_completed": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null
-      },
-      "status": {
-        "type": "string"
-      },
-      "text": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "text",
-      "status"
-    ],
-    "type": "object"
-  }
-}

addedOutput schema / description

Added value: +"Standard response structure for all tools"

removedOutput schema / properties / data / title
```
Removed value: -"Data"
```

changedOutput schema / properties / debug / anyOf

Previous value: -[
-  {
-    "$ref": "#/$defs/ResponseDebug"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Technical execution details",
+    "properties": {
+      "api_calls_made": {
+        "default": 1,
+        "type": "integer"
+      },
+      "api_endpoint": {
+        "type": "string"
+      },
+      "cache_hit": {
+        "default": false,
+        "type": "boolean"
+      },
+      "error": {
+        "anyOf": [
+          {
+            "description": "Structured error information",
+            "properties": {
+              "error_type": {
+                "type": "string"
+              },
+              "message": {
+                "type": "string"
+              },
+              "retry_suggested": {
+                "default": false,
+                "type": "boolean"
+              },
+              "user_message": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "error_type",
+              "message",
+              "user_message"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      },
+      "response_time_ms": {
+        "type": "integer"
+      },
+      "warnings": {
+        "anyOf": [
+          {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null
+      }
+    },
+    "required": [
+      "api_endpoint",
+      "response_time_ms"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / metadata / $ref
```
Removed value: -"#/$defs/ResponseMetadata"
```
addedOutput schema / properties / metadata / description
```
Added value: +"Metadata about the data itself"
```

addedOutput schema / properties / metadata / properties

Added value: +{
+  "count": {
+    "type": "integer"
+  },
+  "data_freshness": {
+    "default": "real_time",
+    "type": "string"
+  },
+  "end_date": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "filters_applied": {
+    "anyOf": [
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "source": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "start_date": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  }
+}

addedOutput schema / properties / metadata / required
```
Added value: +[
+  "count"
+]
```
addedOutput schema / properties / metadata / type
```
Added value: +"object"
```
removedOutput schema / properties / summary / $ref
```
Removed value: -"#/$defs/ResponseSummary"
```
addedOutput schema / properties / summary / description
```
Added value: +"Human-readable insights"
```

addedOutput schema / properties / summary / properties

Added value: +{
+  "action_completed": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  "status": {
+    "type": "string"
+  },
+  "text": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / summary / required
```
Added value: +[
+  "text",
+  "status"
+]
```
addedOutput schema / properties / summary / type
```
Added value: +"object"
```

First observedv1.0.1Feb 1, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It fails to disclose what happens when no item is tracked (e.g., returns null or error), whether the tool is read-only, or any side effects. The output schema exists but is not detailed here.

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

Conciseness3/5

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

The description is a single concise sentence that is front-loaded. However, it is too minimal to be considered well-structured; it adds no value beyond the tool name itself.

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

Completeness2/5

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

Given the presence of an output schema (not shown), the description might be partially complete if the schema provides details. However, it lacks explanation of the debug parameter and overall behavior, making it insufficient for reliable tool selection.

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?

Schema coverage is 0%, meaning the single parameter 'debug' lacks any description. The tool description does not mention this parameter, leaving its purpose and impact entirely unexplained.

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 verb 'Get' and resource 'currently tracked item', making the purpose immediately understandable. However, it does not explicitly differentiate from sibling tools like 'get_time_tracks' or 'time_tracking_summary', which could cause confusion about when to use this specific tool.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'start_time_tracking' or 'get_time_tracks', nor does it mention prerequisites or context.

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