Skip to main content
Glama
Sign In
moamcp

moamcp

by Yorha9e
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

moa_tower_mission

Read a mission by ID or update it with status, blockers, task completion, notes, and scope. Use for mission oversight in multi-agent debates.

Instructions

Read or patch a mission, addressed by its id — the argument is named id (e.g. "M1"), NOT mission_id. With only an id, returns the rendered mission view. Patches go through the store: workers may only patch their own mission; ownership assignment and scope changes are tower-only (scope changes re-run the disjoint check and are logged); a blocker sets the mission blocked; task_done marks the first open task containing that text done.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "caller_agent_id": "<caller_agent_id>",
      "id": "<id>"
    },
    "name": "moa_tower_mission"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMission id (e.g. "M1") — pass it as `id`, not `mission_id`
noteNoAppend a decision-log note
scopeNoTower only: replace the mission scope globs (picomatch — `**` crosses directories). Logged; widens what the merge gate accepts.
statusNoNew lifecycle status
blockerNoReport a blocker (also sets status to blocked)
task_doneNoMark the first open task containing this text as done
workspaceYesThe absolute repo root (main checkout) this tower namespace anchors to. Required on every tower tool — the server cwd is never used as a fallback.
clear_blockersNoClear all recorded blockers
caller_agent_idYesYour engine agent id. The tower tools resolve it against the boot-registered roster (the booted tower, or a spawned worker/reviewer).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.13.0

TDQS

A4.1/5.0
Behavior5/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 an excellent job. It reveals major side effects: patches go through the store, workers only patch their own mission, ownership and scope changes are tower-only, scope changes re-run the disjoint check and are logged, a blocker sets status to blocked, and task_done marks the first open task containing that text done. This is far beyond the schema and gives the agent a clear understanding of consequences.

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 a single, fairly long sentence but well-structured: it front-loads the main purpose, clarifies the id argument, and then lists behavioral rules. Every clause adds useful information; there is no padding. It could be split into sentences for readability, but overall it is appropriately sized for a complex tool with 9 parameters.

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?

The description covers the main read vs patch distinction, return value for reads, and key behavioral rules. Since there is no output schema, mentioning that reads return a rendered mission view is helpful. It does not describe error cases or exactly how patches are triggered, but the schema fills in the parameters. Overall, it is sufficiently complete for an agent to invoke the tool confidently.

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 every parameter, so the baseline is 3. The description does add a little extra context (e.g., task_done behavior, scope change side effects), but these are also partly in the schema. It does not significantly improve semantic understanding beyond what the schema already provides.

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 reads or patches a mission, addressed by id. It is specific about the resource and action, and distinguishes from the many sibling tools by focusing on mission read/update operations. However, it does not explicitly name alternative tools, so it doesn't fully differentiate from similar mission-related tools like moa_tower_plan or moa_tower_progress.

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 description gives clear context: use with an id to view, or with patch parameters to modify. It also explains important constraints like workers only patching their own mission and tower-only ownership/scope changes. It does not explicitly mention alternatives or when not to use it, but the context is strong enough for an agent to decide.

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