Skip to main content
Glama
Sign In

Frostbyte

by dev.getfrostbyte
OverviewDiscussionsAdmin

whats_next

Read-onlyIdempotent

Read your up to five most important next tasks, up to three newest un-reviewed Signals from the last 30 days, and one separate release suggestion. Uses the dashboard's personal ranking and dismissals. Also returns the owner's Current Focus, a goal to weigh that never authorises work the user hasn't asked for. Read-only: never assigns, starts, moves or ships work. Use before proposing what to work on next, unless the user already chose.

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": {
      "projectId": "<projectId>",
      "context": "<context>"
    },
    "name": "whats_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
projectIdYesThe project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so the safety bar is low, yet the description still adds real behavior: the hard result caps (five tasks, three Signals, 30-day window), that results are filtered by the dashboard's ranking and dismissals, and that Current Focus is advisory and 'never authorises work the user hasn't asked for' – a genuine guardrail. It restates read-only in concrete terms ('never assigns, starts, moves or ships work'), which is partly redundant with the annotation, and says nothing about response ordering or size limits beyond the caps.

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?

The first sentence front-loads the payload, the middle sentence covers the guardrail, and the last covers routing – no filler. The 'Current Focus' clause is slightly convoluted in phrasing but every sentence earns its place.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the four result components and their caps. Combined with annotations that cover the safety profile, an agent has enough to call it correctly; only the strict 'context' parameter contract is left to the schema.

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 100%, so the schema already documents both parameters and the baseline is 3. The description adds only indirect meaning – that the output is scoped to the project's ranking and dismissals – and does not flag the strict 15-25 word, third-person, no-PII contract on the 'context' parameter, which is the most likely source of invocation error.

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 names a specific read operation and enumerates exactly what comes back: up to five ranked next tasks, up to three newest un-reviewed Signals from the last 30 days, one release suggestion, and the owner's Current Focus. The ranking source ('the dashboard's personal ranking and dismissals') distinguishes it from generic listers like list_tasks or dashboard_snapshot.

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?

It gives an explicit call condition ('Use before proposing what to work on next') plus an explicit exclusion ('unless the user already chose'), which is precisely the decision an agent needs to route between this tool and the sibling dismiss/restore or list tools.

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

All Frostbyte toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources