Skip to main content
Glama

NEXUS AGI

by link.eblas.nexus
OverviewDiscussionsAdmin

Submit goal plan

submit_goal_plan

Store a plan of steps for a goal. The steps become pending plan steps returned by get_agent_tasks and get_pending_work.

Submitting replaces the goal's current plan: its still-waiting steps are
marked 'superseded' (kept for history) and no longer returned. Resubmit
the full plan to correct it. There is no step limit by default. If any
step is invalid, nothing is stored and the error lists the invalid steps.

Args:
    goal_id: UUID of the goal to plan.
    steps: List of step objects, each with:
        - instruction (str): specific action to carry out.
        - context (dict, optional): relevant context for the step.
        - expected_effect (str): what concretely changes when done.
        - estimated_progress (float 0-1): how much it advances the goal.

Input Schema

NameRequiredDescriptionDefault
stepsYes
goal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses crucial behavior: existing waiting steps are superseded and retained for history, no step limit exists by default, and validation is atomic so invalid steps prevent storage and are listed in the error. This is precisely the kind of mutation context an agent needs.

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?

The description is front-loaded with the core action, then replacement semantics, atomicity, and nested field documentation. The Args block is compact and every sentence adds operational meaning.

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?

For a two-parameter mutation with no output schema, the description is nearly complete: it explains replacement, history retention, validation failure, and field semantics. The one minor gap is not specifying what a successful submission returns, though it implies the steps surface through get_agent_tasks and get_pending_work.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the steps array item is untyped, so the description carries the full burden. It documents goal_id as a UUID and defines every step field with types, optionality for context, and a 0–1 range for estimated_progress.

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 opens with a specific verb and resource: storing a plan of steps for a goal. It distinguishes this from sibling operations by explaining that the steps become pending plan steps consumed by get_agent_tasks and get_pending_work.

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?

It clearly establishes usage context by explaining that submission replaces the goal's current plan and that resubmitting the full plan is the correction mechanism. It does not explicitly contrast itself with update_goal or create_goal, but the plan-step scope is clear.

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

All NEXUS AGI toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources