Skip to main content
Glama

transport_dispatch

Dispatch a workflow target via Nogra Transport. Supports hosted and non-hosted modes with brief, wait, sandbox, and run grouping options.

Instructions

Dispatch a workflow target through Nogra Transport.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoIf true, block until Transport returns or times out in non-hosted/private mode.
briefNoApproved inline brief payload for hosted/stateless dispatch. Preferred when available because hosted storage is not authority.
targetNoWorkflow target role. Hosted V1 uses agent; blank uses the environment default.
dry_runNoIf true, write dispatch packet/receipt previews without invoking the target process.
sandboxNoOptional sandbox override passed to the selected local runtime in non-hosted/private mode.
brief_idNoOptional hosted brief id from the Nogra brief lifecycle. Inline brief payload is preferred when available.
intent_idNoOptional stable intent id used to group related runs.
brief_pathNoApproved local brief path for non-hosted/private dispatch.
project_dirNoExisting project directory used as the target working directory. Default is the y26 repo root./
targetModelNoOptional targetModel override. Blank uses the brief value or anthropic:sonnet.
wait_secondsNoOptional wait duration in seconds when wait is true. Zero uses timeout_seconds plus the runtime grace period.
parent_run_idNoOptional parent Transport run id for child graph linkage.
manager_messageNoOptional Manager instruction or supplement.
timeout_secondsNoMaximum target runtime in seconds before Transport treats the run as timed out.
shared_doctrine_refsNoOptional comma- or newline-separated doctrine reference paths for local execution packets; blank supplies none.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations provided; description does not disclose side effects, mutability, permissions, rate limits, or any behavioral traits beyond the single action line. The parameter descriptions hint at behavior, but the main description is wholly insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise in word count but under-specified for the complexity of the tool (15 parameters, no annotations). It lacks essential context, making it inadequate rather than efficiently lean.

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

Completeness1/5

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

Despite high parameter count and no annotations or output schema visible, the description is a single sentence with no elaboration on behavior, use cases, or expected outcomes. It is far from complete.

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%, and parameter descriptions are detailed, so the description need not add additional meaning. Baseline 3 applies; description does not enhance beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'dispatch a workflow target through Nogra Transport', which is a clear verb and resource, but does not differentiate from many sibling tools like transport_register or transport_update, leaving ambiguity about exactly what 'dispatch' entails.

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?

No explicit guidance on when to use this tool vs alternatives, no prerequisites or exclusions. With 30+ sibling tools, the lack of usage context is a significant gap.

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/nograai/nogra-mcp'

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