Mundane

get_task_status

Read-onlyIdempotent

Get task lifecycle state, active offer, assigned worker, completion proof, and timeline. Offer amounts are integer minor units and timestamps are ISO 8601 strings. Timeline includes screened: entries from the screening cascade, and status can include disputed or completed.

Input Schema

Name	Required	Description	Default
`task_id`	Yes	The owned task to inspect.

Output Schema

Name	Required	Description	Default
`offer`	No
`status`	No
`worker`	No
`task_id`	No
`timeline`	No
`completion`	No
`interactive`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / interactive

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Interactive"
+}

Changed2 schema fields changedSep 22, 2026

addedInput schema / properties / task_id / description
```
Added value: +"The owned task to inspect."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "completion": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Completion"
+    },
+    "offer": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Offer"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Status"
+    },
+    "task_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Task Id"
+    },
+    "timeline": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Timeline"
+    },
+    "worker": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Worker"
+    }
+  },
+  "title": "TaskStatusOut",
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely useful domain context: offer amounts are integer minor units, timestamps are ISO 8601, timeline carries screened:<outcome> cascade entries, and status may be disputed or completed. It does not discuss pagination or limits, but the added format/domain detail is meaningful.

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?

Front-loaded with the core purpose in the first sentence, followed by compact format notes. Three sentences with little waste, though the timeline/status caveats are slightly scattered rather than grouped.

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?

For a read-only status tool with full schema coverage and an existing output schema, the description is complete enough: it clarifies units, timestamp format, and notable status values. Return-value explanation is technically redundant given the output schema, but it does not detract.

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?

Only one parameter (task_id) with 100% schema description coverage ('The owned task to inspect'), so the schema already carries the semantics. The description adds no parameter-level detail beyond the schema; baseline 3 applies.

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?

States a specific verb+resource (get task status) and enumerates the returned facets (lifecycle state, active offer, assigned worker, completion proof, timeline), which implicitly distinguishes it from narrower siblings like get_task_proof or list_task_events. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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 when-to-use or when-not-to-use guidance is given, despite a large sibling set containing close alternatives (get_task_proof, list_task_events, get_chain_status, get_task_chat). Usage is only implied by the tool name and the schema note 'The owned task to inspect'.

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

All Mundane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.