Skip to main content
Glama

Read the activity feed

activity_get
Read-onlyIdempotent

Fetch the newest timeline entries and active reminders for a shared flat so you can review recent expenses, chores, shopping, announcements, and who did what.

Instructions

Returns the newest timeline entries of the flat, 80 by default and up to 320 with limit, plus active reminders. Timeline entries cover expenses, shopping, announcements, chore completions, recurring costs, absences and audit events. Reminders (kind, title, detail, href; top 6, independent of limit) cover open shopping items, overdue chores and open announcements. Use it to see what happened recently and who did it. There are no filters and no cursor; for older history use export_get, for current totals and balances use dashboard_get. Read-only; any member of the connected flat may call it.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of timeline entries to return, from 80 to 320; reminders are not counted. Values below 80 are rejected, because the app raises them to 80 anyway. Omit for the default of 80.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Number of timeline entries to return, from 80 to 320; reminders are not counted. Values below 80 are rejected, because the app raises them to 80 anyway. Omit for the default of 80.",
      +  "maximum": 320,
      +  "minimum": 80,
      +  "type": "integer"
      +}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses that reminders are capped at top 6 independently of limit, that there is no pagination cursor, and that any member of the connected flat may call it. These are behavioral facts the annotations and schema do not convey.

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?

Front-loaded with the core behavior and the return contents, followed by usage and alternatives, with no filler sentences. The enumeration of entry and reminder types is dense but each item carries real selection value, so only minor tightening is possible.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by naming the reminder fields (kind, title, detail, href) and the entry categories returned. For a two-parameter read-only list tool, an agent has everything needed to call it and interpret results.

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 100%, so the schema already documents both limit (80–320, default 80) and wgCode. The description restates the 80 default and 320 ceiling and adds the clarification that reminders do not count against limit, but otherwise adds little meaning beyond the schema text. Baseline 3 applies.

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?

States a specific verb and resource ('Returns the newest timeline entries ... plus active reminders') and enumerates exactly what the entries cover (expenses, shopping, announcements, chore completions, recurring costs, absences, audit events). An agent can distinguish this from export_get and dashboard_get without opening either schema.

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?

Explicitly says when to use it ('to see what happened recently and who did it') and names the two alternatives with the conditions that select them: export_get for older history, dashboard_get for current totals and balances. It also states the exclusion ('no filters and no cursor'), leaving nothing to inference.

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