Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

List Tasks

tasks
Read-onlyIdempotent

List serverless one-off GPU jobs in a workspace or retrieve a specific job by ID, filtering by status and viewing cost, exit code, and output-save progress.

Instructions

List serverless tasks (one-off GPU jobs) in a workspace, or show one by task_id (looks like "task_..."). Filter with status (queued, scheduling, pulling, fetching, running, succeeded, failed, timed_out, stopped); the detail view includes cost and exit code. A task usually goes queued → scheduling → running → succeeded or failed; pulling and fetching show only while an image or the input assets take a while to download. outputs says where saving the task's /outputs files stands, as the console shows it; tell the user its summary. Its phase is running until the task ends; preparing, uploading, retrying or registering while the files are being saved (progress is files_so_far of files_to_upload); then saved (in Assets as asset_name/asset_id), partially_saved, not_saved, discarded or empty. A server without outputs sends output_upload_state instead: "skipped" or null with 0 files doesn't mean nothing was saved — check with download_links(task=...). workspace takes the id from the workspaces tool (a label also works); omit it if the user has only one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo
limitNo
cursorNo
statusNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description explains status lifecycle semantics, output-saving phases including retrying and partially_saved states, the meaning of output_upload_state when outputs is absent, and the ambiguity of null/0-file cases. This is substantial behavioral context that helps an agent interpret results correctly.

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 front-loaded with its primary purpose and organized by concern: listing, status filtering, output semantics, and workspace handling. It is longer than average but most sentences carry operational value, though the dense parenthetical output-state explanation could be tightened.

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 list tool with no schema parameter descriptions and a complex task/output lifecycle, the definition covers most operational context needed to call and interpret the tool. The main gap is pagination guidance for limit and cursor, which matters for a list endpoint.

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?

With 0% schema description coverage, the description compensates for task, status, and workspace by explaining the task_id format, enumerating status values, and pointing to workspaces for workspace IDs. However, the limit and cursor parameters are not described at all, leaving pagination behavior unclear.

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?

The description states a specific verb and resource: listing serverless tasks (one-off GPU jobs) in a workspace or showing one by task_id. It distinguishes the list view from the detail view and names related sibling tools such as download_links and workspaces, making the tool's purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear usage conditions: use task_id to show one task, filter by status, omit workspace if the user has only one, and check download_links when outputs or output_upload_state are null/skipped. It does not explicitly state when not to use this tool versus other task-related siblings, but the guidance is strong.

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