Skip to main content
Glama
Sign In
musterd

musterd

Official
by musterd-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

team_goal_declare

Declare a named team goal to coordinate lanes and dependencies, so status derives from linked work and ordering stays automatic without maintaining ranks.

Instructions

Declare a Goal (a named outcome). Lanes link to it via goal_id; status is derived from them, never stored. Re-declaring the same id amends it (wholesale — pass every field you want kept). depends_on names goals that must ship first; ordering is otherwise automatic (most recently declared first), so there is no rank to maintain.

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": {
      "id": "<id>",
      "title": "<title>"
    },
    "name": "team_goal_declare"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesstable Goal id, e.g. "orientation-spine"
waveNo"later" shelves the goal; omit otherwise (numeric ranks retired, ADR 257)
storyNoplain-language line for outsiders
titleYesthe outcome, short
depends_onNogoal ids that must ship before this one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A3.9/5.0
Behavior3/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 disclose real behavior: status is derived from lanes and never stored, re-declaration replaces all fields, and ordering is automatic. It omits prerequisites (permissions, whether depends_on targets must already exist, cycle handling) and any indication of what a call returns.

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?

Four dense sentences with no filler, and the core definition is front-loaded. The em-dash parentheticals ('wholesale — pass every field you want kept') pack two ideas into one clause, which is efficient but slightly harder to parse than plain sentences.

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 non-obvious semantics an agent needs for a mutation tool with no annotations and no output schema: upsert replacement, derived status, and dependency-driven ordering. What is missing is error and constraint behavior around depends_on, which matters for a tool whose input references other goal ids.

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%, so the schema already documents every parameter, making 3 the baseline. The description adds genuine meaning for 'depends_on' (goals that must ship first, and that ordering is derived rather than ranked) and explains why no rank field exists, but adds nothing about 'wave' or 'story'.

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 verb and resource ('Declare a Goal') and immediately defines what a Goal is ('a named outcome'). The note that re-declaring the same id amends it makes clear this is an upsert, which distinguishes it from team_goal_retract, team_goal_outcome, and the read-only team_goals sibling.

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?

Gives clear context for when to call it (creating or amending a goal) and warns that amendment is wholesale, but never names alternatives such as team_goals for listing or team_goal_retract for removal. Usage is inferable rather than explicit routing.

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