Skip to main content
Glama
Sign In
usap-skills

usap-skills

by jaskaranhundal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dispatch_after_approval

Phase 3 explicit dispatch. After route_payload returned an approval_required decision and the calling client surfaced the prompt to the user, the client calls this to actually invoke the downstream capability.

Instructions

Phase 3 explicit dispatch. After route_payload returned an approval_required decision and the calling client surfaced the prompt to the user, the client calls this to actually invoke the downstream capability. Writes approval_granted + dispatch audit lines so the chain is recoverable end-to-end.

Input Schema

NameRequiredDescriptionDefault
mcp_idYesThe MCP id from the prior route decision.
argumentsNoArguments passed to the capability.
capability_idYesThe capability id to invoke.
approval_tokenNoRequired. The single-use token returned by route_payload in its approval_required decision; bound to that MCP, capability and arguments, valid 60 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.0
    • changedInput schema / properties / approval_token / description
      Previous value: -"Audit token for the approval. Phase 4 will require this to be USAP-signed."New value: +"Required. The single-use token returned by route_payload in its approval_required decision; bound to that MCP, capability and arguments, valid 60 minutes."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses the side effects (approval_granted and dispatch audit lines written, chain recoverable end-to-end) and the approval gate. It stops short of describing failure behavior (expired or reused token), idempotency, or what the call returns, which matters for a dispatch tool with no output schema.

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?

Three tight sentences: the gating condition comes first, then the action, then the audit side effect. Nothing is redundant and the phase label is immediately unpacked.

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

Completeness4/5

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

Covers the workflow position, prerequisites, and persistence side effects for a tool with rich schema coverage and no output schema. The main omission is what the caller gets back and what happens on token expiry or downstream failure.

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 description coverage is 100% and the approval_token field already documents single-use binding and the 60-minute validity, so the description need not repeat it. The description adds no parameter-level guidance beyond what the schema provides, so the baseline applies.

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?

States a specific action ('actually invoke the downstream capability') and places it precisely in the tool chain as the step following route_payload's approval_required decision. An agent can distinguish it from route_payload and validate_payload without inspecting schemas.

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?

Explicitly names the precondition (route_payload returned approval_required and the client surfaced the prompt to the user) and the preceding sibling that produces the input. This is a clear when-to-use rule tied to a named alternative.

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