Skip to main content
Glama
Sign In
PowerShell Empire MCP Server

PowerShell Empire MCP Server

by schwarztim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

empire_task_result

Retrieve the output of a completed task by specifying the agent and task ID, enabling verification of command execution results.

Instructions

Get the result of a specific task

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "task_id": "<task_id>"
    },
    "name": "empire_task_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent ID or name
task_idYesTask ID to get result for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description only states the tool's function without revealing behavior such as blocking, polling, error handling, or side effects. The agent gains no insight beyond the basic action.

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 a single sentence with no unnecessary words. It front-loads the core purpose, but could be slightly expanded to include usage context without becoming verbose.

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 two-parameter tool, the description is minimal. It does not explain return format or error scenarios. Given the absence of an output schema, more detail would help the agent understand what to expect.

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 coverage is 100% with descriptions for both parameters, so the schema already documents their meaning. The description adds no additional context or constraints beyond what is in the input 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 clearly states the verb 'Get' and the resource 'result of a specific task'. It directly reflects the tool's name and is distinct from sibling tools like empire_shell or empire_download, which handle different operations.

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 does not indicate prerequisites (e.g., task must be complete) or contrast with related tools like empire_agents or empire_shell.

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

Deploy Server

Other Tools