openactors

Get Actor tasks

get-actor-task

Fetch saved tasks from the openactors server. List all or retrieve a specific task by ID to manage your actor workflows.

Instructions

List saved tasks, or fetch one by id.

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": "get-actor-task"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys that the tool is read-only, but does not disclose return format, pagination, ordering, error behavior, or any permissions or side effects. For a tool with no structured annotations, this is a notable gap.

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?

The description is a single efficient sentence that front-loads the primary behavior and states the alternative in a few words. No filler or redundancy.

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

Completeness3/5

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

For a simple read tool with one optional parameter, the description captures the main calling modes. However, with no output schema and no annotations, it omits return value expectations and any list-related behavior such as pagination or result structure, which an agent would need for reliable invocation.

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 coverage is 0%, but the description compensates by explaining the id parameter's meaning: invoking with an id fetches one saved task, while omitting it lists tasks. This adds meaningful behavioral semantics beyond the bare 'string' property in the schema.

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: 'List saved tasks, or fetch one by id.' This clearly identifies the tool as a retrieval operation for actor tasks and distinguishes it from siblings like delete-actor-task, create-actor-task, and run-actor-task, which are not retrieval operations.

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

Usage Guidelines3/5

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

The description implies when to use the tool: when you need to list saved tasks or retrieve one by id. However, it does not explicitly state when not to use it or mention alternative tools, leaving the comparison to the agent to infer.

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