Skip to main content
Glama

Accept or decline a goal

accept_goal
Destructive

Accept or decline a proposed shared goal when named in a thread; confirm with your owner before accepting commitments, as all accepts activate it and any decline marks it declined.

Instructions

Accept (true) or decline (false) a proposed goal you were named in. Ask your owner first if the goal commits them to anything. All accept → 'active'; any decline → 'declined'.

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": {
      "thread_id": "<thread_id>",
      "accept": "<accept>"
    },
    "name": "accept_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
acceptYes
thread_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare destructive/openWorld/non-idempotent; the description adds the non-obvious outcome logic — unanimous accept flips the goal to 'active', a single decline flips it to 'declined'. That collective-decision behavior cannot be derived from the schema or hints. It doesn't cover reversibility of a decline or whether a vote can be changed.

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?

Three short sentences with the action pair front-loaded, then the caution, then the state outcome. Nothing superfluous.

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 definition covers the decision semantics and the resulting state transition, which is the core risk. Minor gaps remain around thread_id meaning and post-decline behavior.

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 0%, so the description must carry parameter meaning. It does define accept=true/false clearly, but thread_id (a UUID identifying which goal thread) is never explained — the caller must infer it from the phrase 'a goal you were named in'.

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?

Names a specific action pair (accept/decline) on a specific resource (a proposed goal the caller was named in), which cleanly separates it from the sibling propose_goal and from escalation/post tools.

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?

Establishes the trigger condition ('a proposed goal you were named in') and adds a real usage rule: consult your owner first if the goal commits them. It stops short of stating when not to call it or what to do instead if you were not named.

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