now-sdk-ext-mcp

Get Flow Outputs

get_flow_outputs

Read-only

Fetch output name-value pairs from a completed flow using its context ID. Call only after the flow status shows COMPLETE to get the defined outputs.

Instructions

Retrieve outputs from a completed flow/subflow/action execution by its context ID. Only call this after get_flow_context_status shows COMPLETE.

Returns the output name-value pairs defined by the flow/subflow/action.

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": {
      "context_id": "<context_id>"
    },
    "name": "get_flow_outputs"
  }
}

Input Schema

Name	Required	Description	Default
`instance`	No	The ServiceNow instance auth alias to use. This is the alias configured via `now-sdk auth --add` (e.g., "myinstance", "prod", "test"). The user will typically refer to this by name when saying things like "on my myinstance instance". If not provided, falls back to the SN_AUTH_ALIAS environment variable.
`context_id`	Yes	The flow context sys_id from the execution result's contextId field.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.5.1May 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With readOnlyHint=true, the description adds value by clarifying the return format (output name-value pairs) and the prerequisite status condition. It doesn't disclose failure behavior, but also doesn't contradict annotations.

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?

Two tightly written sentences that front-load the core action and add a key precondition. No redundant phrases or filler.

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 simple read-only retrieval tool with full schema coverage, the description covers what it returns, the precondition, and the resource type. It is sufficient for an agent to know when and how to invoke it.

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 input schema already provides full descriptions for both parameters (context_id and instance), achieving 100% coverage. The description repeats 'context ID' but adds no additional parameter-level detail beyond 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 clearly states 'Retrieve outputs from a completed flow/subflow/action execution by its context ID,' specifying the verb, resource, and key parameter. It distinguishes from sibling tools like get_flow_context_status (status) and get_flow_logs (logs) by focusing on the output values.

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 explicitly conditions usage on get_flow_context_status showing COMPLETE, providing a clear when-to-use rule. It doesn't name alternatives or exclusions, but the precondition is specific and actionable.

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

Deploy Server