Skip to main content
Glama

add

Adds a new undecided position to a Playing to Win box, from aspiration through management systems, and optionally assigns it to a strategy cascade.

Instructions

Add a position into a box — 1 aspiration, 2 where to play, 3 how to win, 4 capabilities, 5 management systems (number or name). It arrives undecided. Optional cascade: add it to that strategy.

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": {
      "title": "<title>",
      "box": "<box>"
    },
    "name": "add"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxYes
titleYes
sourceNo
cascadeNo
statementNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 ('arrives undecided') and that cascade is optional, but says nothing about permissions, duplicate handling, or what the write affects — meaningful gaps for a mutation tool.

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?

Two tight sentences with the core action front-loaded and no filler. The inline numeric enumeration is dense but readable, and nothing is wasted.

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?

The output schema covers return values, and box/cascade are explained, but for a five-parameter tool at 0% schema coverage the absence of any explanation of source and statement leaves real holes an agent would notice.

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 coverage is 0%, so the description must compensate. It does decode the otherwise opaque `box` values and clarifies `cascade`, but leaves title, source, and statement completely undescribed — a partial compensation for five parameters.

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?

Names a specific verb and resource ('add a position into a box') and goes further by enumerating the five box values with their meanings, which no structured field supplies. It does not explicitly distinguish itself from siblings such as adopt or evidence_add, so it stops short of a 5.

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?

'It arrives undecided' and the optional cascade clause imply when to reach for this versus adopt or cascade_create, but the agent must infer that linkage. No explicit when-not guidance or named alternative is given.

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