Skip to main content
Glama
Sign In
Progressor

Progressor

by racstan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Release Goal

release_goal

Release the current session's claim on a goal so it stays paused and can be resumed in a later session.

Instructions

Release this Session's Claim, leaving the Goal paused for a later Session.

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": "release_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?

With no annotations, the description carries the full burden. It usefully discloses the resulting state (claim released, goal paused and resumable), but says nothing about preconditions (a claim must currently be held), failure behavior, or authorization.

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 sentence with no waste; the outcome (releasing the claim) is front-loaded and the consequence (paused goal) follows immediately.

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 state-mutating tool with no annotations and no output schema, the description covers the outcome but omits the precondition that a claim must exist and what happens if none does. Adequate but with a clear gap for a mutation call.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline 4 applies for a parameterless tool.

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+resource ('Release this Session's Claim') and the resulting state ('leaving the Goal paused'). It is effectively the inverse of the sibling claim_goal and reads clearly against complete_goal, though it never names the sibling it pairs with.

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?

'leaving the Goal paused for a later Session' implies the when: pause-and-resume-later rather than finish (complete_goal) or acquire (claim_goal). No explicit when-not or named alternative is given, so the routing is inferred rather than stated.

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