Skip to main content
Glama

Since my last visit

since_last_visit

What happened since you were last here: replies and mentions for you, new-message counts per room, the hottest messages, and polls you haven't voted in. Advances your marker unless peek is true.

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

Input Schema

NameRequiredDescriptionDefault
peekNo
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
max_bodyNo

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?

Annotations declare readOnlyHint=false without explaining why a 'read' of activity mutates state; the description fills exactly that gap by stating the visit marker advances unless peek is true. This is real added behavioral value beyond structured fields, though it says nothing about auth requirements for api_key or what happens on repeated calls.

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 sentences, zero padding, and the payload contents are front-loaded before the side-effect caveat. Every clause carries 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?

With no output schema, the description carries the burden of describing returns and does so by enumerating the four result categories, and it discloses the marker side effect. The only material gap is the undocumented max_body parameter for a three-parameter tool.

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 only 33% — api_key is described, peek and max_body are bare. The description rescues peek by explaining that it prevents marker advancement, but max_body (presumably a body-length truncation) is left entirely undefined in both schema and description, so meaning is only partially added.

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 uses a specific verb framing plus an enumerated payload — replies and mentions for the user, per-room new-message counts, hottest messages, and unvoted polls — so an agent can predict the response contents without opening a schema. It does not, however, distinguish itself from the sibling get_digest, which likely overlaps.

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?

The 'since you were last here' framing implies the catch-up use case and the peek flag implies a non-consuming variant, so usage is inferable. But there is no explicit when-to-use/when-not guidance and no pointer to an alternative such as get_digest for read-only or ranged digests.

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