Skip to main content
Glama

set_later

Move a specced project to the backlog so it stays off the home view until work begins. Set later to true to park it, or false/hand_over to restart it when ready.

Instructions

Keep a specced project for later: the person's backlog, off their home until it is started. Call it when the person says the project is for later, not to build now, and never on your own judgment. later=False (or hand_over) starts it again. Refused for a project the crew already has, and for a finished one.

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": "set_later"
  }
}

Input Schema

NameRequiredDescriptionDefault
laterNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

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 must carry the full burden and it does disclose the key behaviors: the project leaves the person's home, the change is reversible via later=False or hand_over, and the call is refused for crew-owned or finished projects. It does not say whether project data/state is preserved or discarded while in backlog, nor whether the operation requires confirmation, so the behavioral picture is helpful but incomplete.

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?

Front-loaded with the purpose, then the call condition, then the reversal and refusal cases; nothing is padding. The refusal sentence is dense and would read better as its own line, but no wording is wasted.

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-param state-toggle tool with no annotations and an output schema that carries return values, the description covers purpose, trigger, reversal, and refusal cases. The single remaining gap is how the target project is identified, which matters because the parameter has an empty default.

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 has to compensate and it only partly does: it clarifies the polarity of 'later' ('later=False ... starts it again'), which is genuinely valuable for a boolean flip. It says nothing about the 'project' parameter — whether it is a name, id, or how an empty default is resolved — leaving half the inputs undocumented in both schema and description.

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 concrete verb and resource — keeping a specced project for later so it sits in the person's backlog and off their home — and distinguishes the operation from hand_over by naming it as the restart path. The domain jargon ('specced project', 'crew') leaves the object slightly opaque, but the effect of the call is unambiguous.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the person says the project is for later, not to build now'), an explicit exclusion ('never on your own judgment'), and names the alternative path (hand_over / later=False) for the opposite direction. The refusal conditions for crew-owned and finished projects further pin down when the call is valid.

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