@contextq/mcp

Official

Overview Schema Source Related Servers Discussions Admin

goal_frontier

Identify startable work: return goal nodes with all blocking dependencies done and not complete, filtered by role, project, or objective run; external-blocker nodes stay blocked.

Instructions

The ready-frontier: nodes (optionally for a role, or scoped to one objective_run_id) whose ALL blocking dependencies are done and that aren't done yet — i.e. 'what can I start NOW'. Returns GoalNode[] with depsIn/depsOut ([{nodeId, kind}]). A node whose externalRef.blocker is set is waiting on a person or an external event, not on a dependency: treat it as not runnable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "goal_frontier"
  }
}

Input Schema

Name	Required	Description
`owner_role`	No	Filter to a role's ready work
`project_id`	No	Filter by project
`objective_run_id`	No	Scope to one objective's run id

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Oct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (GoalNode[] with depsIn/depsOut as [{nodeId, kind}]) and a meaningful behavioral nuance that nodes with externalRef.blocker are waiting on external events. It doesn't cover pagination or limits, but for a read tool the disclosure is substantial.

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?

Front-loaded with the core definition before qualifiers, and every clause (role/run_id scoping, return shape, blocker caveat) earns its place. The single long sentence is dense but not padded.

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?

With no output schema, the description correctly compensates by naming the return type and its fields. The blocker caveat adds operational detail an agent needs. Only minor gaps (pagination/limits) remain for this zero-annotation read 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 description coverage is 100%, so the schema already documents all three parameters. The description reinforces owner_role ('optionally for a role') and objective_run_id ('scoped to one objective_run_id') but ignores project_id entirely, adding nothing beyond what the schema provides. Baseline 3 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?

The description defines a specific, non-obvious concept ('the ready-frontier') and states the exact semantics: nodes whose blocking dependencies are all done. It effectively distinguishes the tool from siblings like goal_list and goal_advance by answering 'what can I start NOW'.

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 phrasing 'what can I start NOW' makes the use case clear, and the externalRef.blocker note tells the agent when a frontier node should NOT be treated as runnable. It does not, however, explicitly contrast this tool with goal_list or other goal siblings, leaving the routing decision partly to inference.

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