Skip to main content
Glama

KanbanMCP

Read recent activity

events_since
Read-onlyIdempotent

Reads board activity after a cursor. Call it between steps to see what changed.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoThe last event id you saw. Default 0.
boardIdNoBoard id or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the polling workflow ('between steps') and the incremental-cursor model, but says nothing about event ordering, replay, or how to obtain the next cursor. With annotations carrying the safety burden, this is adequate but thin.

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 short sentences, zero padding, with the mechanism (cursor) front-loaded and the invocation cue second. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should say something about what comes back and how to advance the cursor, but it leaves both implicit. It is sufficient to invoke the tool correctly (both params are optional with sane defaults) yet incomplete for driving the polling loop it prescribes.

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 cursor ('last event id you saw, default 0') and boardId are fully documented in the schema. The description's 'after a cursor' phrasing reinforces the cursor semantics but adds no format, ordering, or default details beyond structured data — the baseline 3.

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?

States a specific verb and resource ('reads board activity') plus the cursor-based scope ('after a cursor'), which clearly separates it from siblings like inbox, heartbeat, or get_context. It does not explicitly name an alternative tool, so it stops short of a 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 between steps to see what changed' gives an explicit usage moment, which is unusually actionable for a polling tool. It offers no when-not guidance or named alternatives, so it falls short of a 5.

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