Skip to main content
Glama

dispatch_handoff

Builds a handoff bundle from a public brief for a specified target, including optional doctrine references and metadata, to prepare material for a runtime without executing work.

Instructions

Build a public dispatch handoff.

    Bundles an existing public brief, caller-defined target, optional linkage, optional doctrine text, and metadata
    into a self-contained handoff for a caller-owned runtime. In plugin mode, this handoff is material for
    a customer-side ephemeral subagent; it is not permission for Manager to execute the scope inline.

    When to use:
    - Prepare a saved public brief for handoff to a runtime without requiring another MCP read.
    - Include small workspace-local reference files beside the embedded brief content.
    - Support a plugin-mode Manager -> ephemeral executor crossing when dispatch handoff material is useful.

    When NOT to use:
    - Do not use this to execute work; it only builds a handoff.
    - Do not use this without a saved brief; use transport_register directly for brief-less tracking.
    - Do not use this as a fallback after subagent spawning fails.

    Examples:
    >>> dispatch_handoff("brief-import-audit-2026-05-06-a1b2c3", "audit-job")
    {"schema": "nogra.dispatch.handoff.v1", "target": "audit-job", "brief": {...}, ...}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesFree-form caller-defined runtime target.
brief_idYesPublic brief id to embed into the dispatch handoff.
metadataNoOptional caller-owned handoff metadata.
intent_idNoOptional caller-owned intent id.
doctrine_refsNoOptional workspace-relative doctrine file refs to embed.
parent_run_idNoOptional parent transport run id for caller linkage.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. Discloses that the tool only builds a handoff, does not execute, requires a saved brief, and is for plugin-mode crossing. No contradictions.

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?

Well-structured with main description, usage guidelines, and example. Every sentence adds value, no redundancy, front-loaded with purpose. Concisely comprehensive.

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?

Given 6 parameters, no annotations, and an output schema (example provided), the description covers when/why/how, includes an example output, and distinguishes from siblings. Missing error cases, but overall sufficient for correct invocation.

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?

Schema description coverage is 100%, baseline 3. Description adds value by elaborating on parameter roles (e.g., 'caller-defined runtime target', 'optional linkage') and providing an example with parameter values, though schema already has decent descriptions.

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 tool builds a public dispatch handoff, bundles a brief, target, and optional fields. It distinguishes from sibling tools by emphasizing it does not execute work and is specific to handoff preparation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to use' and 'When NOT to use' sections with bullet points. Provides clear contexts, exclusions (e.g., not for execution), and mentions alternative tool (transport_register) for brief-less tracking.

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