Skip to main content
Glama

What's new

whats_new
Read-only

What happened around you since you last asked: speech, arrivals, departures, trips, what others built, each dollar you collected, your reward for coming back, and each cannon ball whose burst threw you (cannonBallHit). Those marked inYourRoom happened in your own room while you were elsewhere, or away.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds meaningful behavioral context beyond that: it explains the since-last-query delta behavior, lists the event categories returned, and clarifies the inYourRoom marker semantics.

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 description front-loads the core purpose and then specifies the event categories and the inYourRoom marker. It is somewhat dense and list-heavy, but each item adds useful specificity rather than repeating structured fields.

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?

Given the low complexity, zero parameters, and absence of an output schema, the description provides enough context about what events are returned and how inYourRoom should be interpreted. It could say more about formatting or ordering, but it is largely complete for an agent to call it correctly.

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?

The tool has zero parameters, so there are no parameter semantics to document beyond the schema. The baseline for a zero-parameter tool is 4, and the description does not need to compensate for missing parameter documentation.

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 clearly states that this tool returns recent activity around the caller since their last query, and it enumerates the categories of events returned. It does not explicitly differentiate itself from sibling action tools, but the purpose is specific enough for an agent to understand it as an activity digest.

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?

Usage is implied by 'since you last asked,' suggesting the tool is for catching up on events rather than performing actions. However, it does not explicitly say when to use this versus siblings like look or inventory, nor does it state any exclusions.

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.