Skip to main content
Glama

chain_pm_then_agent

Chain a Project Manager review and an Agent execution under one chain ID, ensuring persistent state across phases for brief-led development.

Instructions

Chain PM -> Agent under a single chain id with persistent chain-state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefNoApproved inline brief payload for hosted/stateless dispatch. Preferred when available because hosted storage is not authority.
brief_idNoOptional hosted brief id from the Nogra brief lifecycle. Inline brief payload is preferred when available.
intent_idNoOptional intent id forwarded to Agent for run-graph linkage.
brief_pathNoApproved brief path. Required for chain dispatch.
project_dirNoExisting project directory where the PM and Agent phases run./
targetModelNoOptional targetModel override. Blank uses the brief value or anthropic:sonnet.
manager_messageNoOptional Manager instruction or supplement passed to both chain phases.
timeout_per_phase_secondsNoMaximum runtime per chain phase (PM execute, Agent execute) in seconds.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It mentions persistent chain-state and single chain id but omits critical details such as destructive potential, authentication requirements, error handling, or consequences of incorrect parameters.

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 extremely concise at one sentence, containing no wasted words. However, it could be slightly expanded to include structured guidance without losing brevity.

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

Completeness2/5

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

Despite the existence of an output schema and rich input parameters, the description lacks essential context about the chain lifecycle, parameter interplay, and prerequisites. This is insufficient for an agent to reliably invoke the tool.

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 detailed descriptions for all 8 parameters. The tool description adds no additional parameter semantics beyond what is already in the schema, so a baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool chains PM and Agent phases under a single chain id with persistent chain-state, distinguishing it from standalone dispatch tools. However, the terms 'PM' and 'Agent' are not explicitly defined, which may cause ambiguity for unfamiliar agents.

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 guidance is provided on when to use this tool versus alternatives like 'dispatch_handoff' or 'agent_exec_packet'. With 29 sibling tools, the lack of usage context makes it difficult for an agent to select the correct tool.

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