Skip to main content
Glama
nanoseil

MCP Background Task Server

by nanoseil

Get Task Stdout

get-task-stdout

Retrieve the standard output from a running background task to monitor its execution status and results.

Instructions

Retrieves the stdout of a running background task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesUnique name of the task

Implementation Reference

  • The handler function retrieves the Child process instance for the specified task name and returns its accumulated stdout, or an error message if no such task exists.
    async ({ name }) => {
      const child = processes.get(name);
      if (!child) {
        return {
          content: [
            {
              type: "text",
              text: `No task found with name "${name}".`,
            },
          ],
        };
      }
    
      return {
        content: [
          {
            type: "text",
            text: `Stdout of task "${name}":\n${
              child.stdout || "No output yet."
            }`,
          },
        ],
      };
    }
  • Input schema definition for the tool, specifying the required 'name' parameter as a string with Zod validation, along with title and description.
    {
      title: "Get Task Stdout",
      description: "Retrieves the stdout of a running background task.",
      inputSchema: {
        name: z.string().describe("Unique name of the task"),
      },
    },
  • src/index.ts:181-214 (registration)
    The server.registerTool call that registers the 'get-task-stdout' tool, including its name, schema, and handler implementation.
    server.registerTool(
      "get-task-stdout",
      {
        title: "Get Task Stdout",
        description: "Retrieves the stdout of a running background task.",
        inputSchema: {
          name: z.string().describe("Unique name of the task"),
        },
      },
      async ({ name }) => {
        const child = processes.get(name);
        if (!child) {
          return {
            content: [
              {
                type: "text",
                text: `No task found with name "${name}".`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: "text",
              text: `Stdout of task "${name}":\n${
                child.stdout || "No output yet."
              }`,
            },
          ],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Retrieves' implies a read operation, it doesn't specify whether this requires specific permissions, what happens if the task isn't running or doesn't exist, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 single-parameter read operation with no output schema, the description is minimally adequate but has clear gaps. It doesn't explain what format the stdout returns in, whether it's paginated, or what happens with non-existent tasks. The absence of annotations means the description should do more to compensate.

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?

The schema description coverage is 100%, with the single parameter 'name' clearly documented as 'Unique name of the task' in the schema. The description doesn't add any additional parameter context beyond what the schema provides, so the baseline score of 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the action ('Retrieves') and resource ('stdout of a running background task'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'get-task-stderr' which retrieves stderr instead of stdout, missing an opportunity for sibling distinction.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention that 'get-task-stderr' retrieves error output instead, or that 'list-background-tasks' might be needed first to identify task names. No usage context or exclusions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nanoseil/mcp-bgtask'

If you have feedback or need assistance with the MCP directory API, please join our Discord server