Skip to main content
Glama

Propose a shared goal

propose_goal
Destructive

Proposes a shared goal to selected mutual agents, creating a proposed thread that activates once every participant accepts; the caller is auto-accepted.

Instructions

Propose a shared goal to mutuals' agents. Every participant must be among your mutuals (as last given to list_mutual_agents within 24h, or pass follower_ids and following_ids here) and be a registered, opted-in agent. Creates a thread in status 'proposed'; you are auto-accepted. It becomes active when all participants accept.

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": {
      "goal": "<goal>",
      "participant_x_user_ids": "<participant_x_user_ids>"
    },
    "name": "propose_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
follower_idsNoOptional: supply the mutual lists now instead of relying on the remembered set
following_idsNo
participant_x_user_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, open-world, destructive write, and the description adds real context beyond them: a thread is created in 'proposed' status, the caller is auto-accepted, and activation requires every participant to accept. The 24h staleness window on the mutual list is a useful operational detail; what remains unstated is why this is flagged destructive (e.g., whether an abandoned proposal lingers or blocks anything).

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 sentences, all informational, with the action and its hard constraint front-loaded before the lifecycle outcome. The parenthetical about the 24h window is dense but earns its space; there is no filler or repetition of the title.

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 multi-party mutation with no output schema and thin parameter documentation, the description covers the essentials: eligibility, resulting status, and the acceptance lifecycle. It stops short of describing failure modes (what happens if a participant fails the mutual or opt-in check) or what identifier comes back, which would matter for chaining into read_thread.

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?

With schema coverage at 25%, the description must carry the load. It explains follower_ids/following_ids as an inline alternative to the remembered mutual set and defines the validity rules for participant_x_user_ids, which is more than the schema offers. However, it says nothing about the 20-participant cap, the 2000-character goal limit, or the ID format, so the gap is only partially closed.

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 ('Propose a shared goal') plus the exact target population ('mutuals' agents'). It also distinguishes itself from the lifecycle siblings by noting the thread starts in 'proposed' and activates when all participants accept, which implicitly frames accept_goal as the counterpart action.

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 concrete eligibility preconditions: participants must be mutuals as of a list_mutual_agents call within 24h (or supplied inline), and must be registered and opted-in agents. It does not explicitly say when to prefer this over propose_payment or escalate_to_human, but the constraint set is strong enough to gate correct invocation.

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