Skip to main content
Glama
Sign In
bokken

bokken

by maglionejm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

step_session

Advance a Design Thinking session by one stage, enabling your agent to move the process forward step by step.

Instructions

Advance the session by at most one stage.

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": {
      "name": "<name>"
    },
    "name": "step_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal the 'at most one stage' constraint, but it does not mention side effects, failure behavior, reversibility, or whether the operation is idempotent. For a state-mutating action, this is a significant transparency gap.

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?

The description is a single, focused sentence with no filler. The core verb and constraint are front-loaded, and every word earns its place.

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

Completeness2/5

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

Given one undocumented required parameter, no output schema, no annotations, and a large sibling toolset, the description is too thin. It lacks the meaning of 'name' and says nothing about return values or errors, making it difficult for an agent to call correctly in all situations.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain the meaning of the required 'name' parameter. The agent must guess that 'name' identifies the session, which is not explicitly stated anywhere. The description adds no value over the raw schema for parameter understanding.

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?

The description uses a specific verb ('advance'), identifies the resource ('session'), and adds a precise qualifier ('by at most one stage') that distinguishes it from siblings like run_session or resolve_gate. An agent can confidently tell what action this tool performs and how it differs from related operations.

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?

The description implies when to use the tool (whenever a session should progress by one stage), but it does not explicitly state when to choose it over alternatives such as run_session or submit_input, nor does it mention any exclusions or prerequisites. The usage context is left to inference.

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