Skip to main content
Glama

Start the next research round

inspo_next_round

Advance the board to the next round so newly added items are grouped separately while older rounds stay browsable; call it before searching again based on feedback.

Instructions

Bump the round number so new items are grouped as "Round N" on the board (older rounds stay browsable). Call before searching again based on feedback.

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

Input Schema

NameRequiredDescriptionDefault
focusNoWhat this round explores, shown on the board.
sessionNoSession id. Defaults to the most recent session in this project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.8/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 behavioral burden. It does disclose a meaningful trait beyond the schema: prior rounds remain browsable after the bump, so the operation is additive rather than destructive. However, it says nothing about what happens to items not yet categorized, whether the call is idempotent, or what the response contains, which leaves real gaps for a state-mutating tool.

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?

Two short sentences with no filler: the effect and the browsability guarantee come first, the invocation guidance second. Every clause contributes information an agent needs.

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-parameter, zero-required tool with no output schema and no annotations, the description covers what changes, what is preserved, and when to call it. The main remaining gap is return behavior and any permission or session-precondition requirements, which an agent must discover by calling.

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 100%, so both parameters (focus, session) are already fully documented in the schema, including the session default. The description mentions neither by name and adds no format or interaction detail, so the baseline 3 applies.

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 action (bump the round number) and its observable effect (new items grouped as "Round N" on the board). It also notes that older rounds stay browsable, so an agent knows this is a state advance rather than a destructive reset. It does not explicitly name which sibling performs the subsequent search, so it falls short of full sibling differentiation.

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

Usage Guidelines4/5

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

"Call before searching again based on feedback" gives a clear trigger condition and ordering constraint relative to the feedback and search tools. There are no explicit when-not conditions, but the sequencing guidance is concrete enough to act on without inference.

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