Skip to main content
Glama

lunara_next_step

Read-onlyIdempotent

Tell me what to call next. Given a jobId (or nothing), returns ready-to-paste tool calls with the exact arguments, plus one line of why. Use this when you are unsure of the order — or just read the "next" array that every mutating tool already returns. Free.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNoOptional. The job you are working on. Omit it if you have not started one yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, non-open-world call, so the safety profile is covered structurally. The description adds what annotations cannot: the return payload contains executable tool calls with exact arguments plus a rationale line, and the 'Free' note signals no cost/quota impact. It does not cover pagination or staleness of recommendations, but those are minor here.

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?

Three short sentences, front-loaded with the core behavior, then the return shape, then the usage rule and alternative. The trailing 'Free' is a minor flourish but earns its place as cost information; nothing is padded.

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 one-optional-parameter, no-output-schema advisory tool, the description covers what it returns, when to call it, and how it relates to the embedded 'next' arrays in mutating tools. Given there is no output schema, an example of the returned call payload would have closed the remaining gap.

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% and the single optional jobId is fully documented in the schema, so the baseline is 3. The description does add one nuance absent from the schema text: passing nothing is valid when a job has not been started yet ('Given a jobId (or nothing)'), which maps a param decision to a workflow state.

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?

The description states a concrete function: given an optional jobId, it returns ready-to-paste tool calls with exact arguments plus a one-line rationale. This distinguishes it from the sibling execution tools (lunara_segment, lunara_translate, etc.) by framing it as an advisory/router tool rather than an action, though the opening 'Tell me what to call next' is conversational rather than precise about the resource.

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?

It gives an explicit trigger ('Use this when you are unsure of the order') and names an alternative path ('read the "next" array that every mutating tool already returns'), which is genuine routing guidance. It does not state conditions where the tool should be avoided entirely, but the alternative it points to covers the main case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources