Skip to main content
Glama

Last Update Tool

last_update
Read-only

Reads the context needed to draft a status update—previous update, since time, open and new tasks, today's start, and next steps—without saving, so you can draft before logging the confirmed update.

Instructions

Reads the context for writing a status update (/upd), without saving anything: the person's own last update on the project, the moment to report from ("since", for git log --since), their open and newly assigned tasks, today's start time and next_steps (the exact steps to follow). Call it first, before drafting; then log_update saves the confirmed draft. Not for a single day's view (my_day) or a project overview (project_brief). If no project can be found from repo, project or session, it returns an error that says how to pick one.

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

Input Schema

NameRequiredDescriptionDefault
repoNoThe output of git remote -v in the working directory (all remotes; one URL also works). Preferred: it finds the project by itself.
projectNoProject slug or name, when there is no repo or it is not linked to a project.
sessionNoThis session's id, from the cemainou line at the start of the session. The session's project wins over the repo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description reinforces it with 'without saving anything' while adding real behavior: the return payload shape and the failure mode ('returns an error that says how to pick one' when no project resolves). What's missing is any note on size/pagination or latency for the multi-source aggregation, but the safety and error profile is genuinely enriched beyond the annotation.

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?

Purpose and the 'call it first' instruction are front-loaded, and every sentence carries routing or contract information. It runs long as a single dense paragraph with heavy parenthetical enumeration, which costs some scannability.

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 listing the returned fields and the 'since' semantics. Combined with the disclosed error path and the guidance on resolving the project, an agent has everything needed to call this correctly on the first try.

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% and the schema itself already documents repo preference, project fallback, and that 'The session's project wins over the repo' — the description repeats rather than extends this. The only added meaning is on the output side ('since', for git log --since), which doesn't deepen the input parameters.

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 ('Reads the context for writing a status update (/upd)'), then enumerates exactly what it returns (last update, since-moment, tasks, today's start, next_steps). It explicitly distinguishes itself from log_update, my_day and project_brief, so an agent can route to it without opening a 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?

'Call it first, before drafting; then log_update saves the confirmed draft' gives an explicit ordering and names the follow-up tool. It also states exclusions positively ('Not for a single day's view (my_day) or a project overview (project_brief)'), covering both when-to-use and when-not-to.

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