Sora Commander

Overview Schema Source Related Servers Discussions Admin

list_tasks

Lists the Owner’s task presets—name, description, and exact command each runs—so you can pick a listed name for run_task. Read-only; returns tasks_configured false when no presets exist.

Instructions

List the Owner's task presets: name, description and the exact command each one runs.

Read-only, no approval window. The Owner writes the presets by hand in a local file read at startup; no tool can add or change them. Use a listed name with run_task. tasks_configured is false when the Owner has no presets.

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": "list_tasks"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.5Nov 10, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations present, the description carries the full burden and does so: it declares the operation read-only with no approval window, explains that presets are hand-written in a local file read at startup, and states no tool can add or change them. The tasks_configured=false sentinel is a genuinely useful signal for the empty state.

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?

Three short sentences, front-loaded with what the tool returns, followed by safety and provenance, then the empty-state flag. No sentence is filler; each adds a distinct fact.

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

Completeness5/5

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

For a zero-argument read tool, the definition covers return content, mutability constraints, provenance of the data, and the empty case. An output schema exists, so return-value structure is already documented and the description need not restate it.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description does not waste words on a schema that is already empty and fully covered.

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?

States a specific verb and resource ('List the Owner's task presets') and immediately enumerates the returned fields (name, description, exact command). The follow-up 'Use a listed name with run_task' separates it unambiguously from the sibling that executes presets.

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?

Gives clear use context: discover presets first, then pass a listed name to run_task, and explains the empty case via tasks_configured=false. It lacks an explicit 'do not use this if...' exclusion, but the run_task pairing covers the practical routing decision.

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