There's An AI For That

Get task details

get_task

Read-only

Get public details for one TAAFT task category by slug. Preserve returned URLs exactly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The task slug returned by search_tasks.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`task`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

addedOutput schema / properties / task / properties / attributes / properties / related_devices

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "availability": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "entity_type": {
+        "type": "string"
+      },
+      "id": {
+        "type": "integer"
+      },
+      "maker": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": "string"
+      },
+      "price": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "price_currency": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "primary_use_cases": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "tasks": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "id": {
+              "type": "integer"
+            },
+            "name": {
+              "type": "string"
+            },
+            "role": {
+              "enum": [
+                "primary",
+                "secondary"
+              ],
+              "type": "string"
+            },
+            "slug": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "slug",
+            "role",
+            "url"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "types": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "entity_type",
+      "name",
+      "slug",
+      "url",
+      "description",
+      "price",
+      "price_currency",
+      "types",
+      "primary_use_cases",
+      "maker",
+      "availability",
+      "tasks"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / task / properties / attributes / properties / related_robots

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "availability": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "description": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "entity_type": {
+        "type": "string"
+      },
+      "id": {
+        "type": "integer"
+      },
+      "maker": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": "string"
+      },
+      "price": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "price_currency": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "primary_use_cases": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "tasks": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "id": {
+              "type": "integer"
+            },
+            "name": {
+              "type": "string"
+            },
+            "role": {
+              "enum": [
+                "primary",
+                "secondary"
+              ],
+              "type": "string"
+            },
+            "slug": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "id",
+            "name",
+            "slug",
+            "role",
+            "url"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "types": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "entity_type",
+      "name",
+      "slug",
+      "url",
+      "description",
+      "price",
+      "price_currency",
+      "types",
+      "primary_use_cases",
+      "maker",
+      "availability",
+      "tasks"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

AddedSep 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that: results are 'public' only, and returned URLs must be preserved exactly. It still says nothing about error behavior or lookup failure, so it is additive but not rich.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the output-handling caveat second. Every sentence earns its place.

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?

An output schema exists, so return values need not be described, and the annotations cover the read-only safety profile. For a single-parameter lookup tool the description is nearly complete; only the missing usage guidance keeps it from a 5.

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% and there is only one parameter, so the schema fully documents 'slug' as 'the task slug returned by search_tasks.' The description adds no format or validation detail beyond that, which is the expected baseline when the schema does the work.

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 and resource ('Get public details for one TAAFT task category by slug'), so an agent knows exactly what it retrieves. It does not explicitly differentiate itself from the many sibling get_* tools (get_tool, get_company, etc.) beyond the 'task category' resource name, but the resource 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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative. The only workflow hint ('slug returned by search_tasks') lives in the schema, not the description, so the agent gets no routing help from the prose.

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

All There's An AI For That 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.