Assay

whats_new

Idempotent

What happened to your tasks since you last looked: work that came back and waits for your word, an attempt that failed, an award. Call it once at the start of a session and tell the person anything it returns before doing what they asked. Reading it marks it seen.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, and the description explains why: "Reading it marks it seen," disclosing a state-changing side effect that the boolean flags alone do not convey. This is genuine added context beyond structured fields, though it says nothing about auth or error behavior.

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 that front-load the payload description before the invocation guidance. Slightly prose-y phrasing ("waits for your word") but nothing is wasted.

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?

No output schema and no parameters, so the description carries the return-value burden — and it does by enumerating the kinds of items returned. It is adequate for an agent to call and report correctly, missing only detail on volume or ordering of returned items.

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

Parameters4/5

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

Zero parameters, so there are no semantics to document and the baseline is 4. The description correctly implies no arguments by describing a once-per-session call with no inputs.

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 gives a concrete verb+resource: it reports task events (returned work awaiting a reply, a failed attempt, an award) that occurred since the last look. The examples make the payload concrete. It is not explicitly differentiated from siblings like my_standing or find_work, so it lands at 4 rather than 5.

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 it once at the start of a session and tell the person anything it returns before doing what they asked" is an explicit trigger and ordering instruction — a strong when-to-use. It stops short of naming alternatives or when-not-to-call, so not a full 5.

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

All Assay tools Inspect

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.