Skip to main content
Glama
Sign In
Progressor

Progressor

by racstan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Complete Goal

complete_goal

Marks the claimed goal as done and releases it, letting Progressor record completion and clear focus for the next task.

Instructions

Mark the claimed Goal done and release it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "complete_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does usefully disclose the compound effect of marking done AND releasing the goal (a side effect not visible in the empty schema), but it says nothing about irreversibility, required permissions, or what happens if no goal is currently claimed.

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?

A single short sentence with the action and its side effect front-loaded. No filler, nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param mutation with no annotations and no output schema, the description covers the action but omits the error/precondition behavior (what if the goal is not claimed) and how it relates to release_goal. Adequate but with clear gaps.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies the target is implicit rather than passed as an argument.

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?

States a specific verb ('Mark ... done') plus a compound effect ('release it') on a specific resource (the Goal). The word 'Goal' does distinguish it from the sibling complete_task, but it does not explicitly differentiate from release_goal, which overlaps on the release half of the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'the claimed Goal' signals a precondition that a goal must first be claimed (via claim_goal). It never states when to prefer this over release_goal or complete_task, so the agent must infer the 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