Skip to main content
Glama

Log a finish or repeat

log_event

Log a completion or a re-watch/re-read/re-listen with a date. Use when the user mentions finishing something again ("watched Heat again last night", "reread Dune"). The first finish is tracked by status; this records repeats so they show in history and stats.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media_type": "<media_type>"
    },
    "name": "log_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional note about this viewing.
titleNoThe title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)
ratingNoOptional rating for this viewing, in stars: 0.05 to 5 in steps of 0.05 (half stars, or a score out of ten divided by two).
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
event_dateNoDate it happened: YYYY-MM-DD, or just YYYY-MM or YYYY when that is all the user knows. Omit if unknown.
event_typeNoWhat happened. Defaults to 'finished'. reread/relistened/rewatched all count as a repeat.
media_typeYesType of media

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  3. Changed3 schema fields changed
    • changedInput schema / properties / rating / description
      Previous value: -"Optional rating for this viewing (0.5 to 5, half-stars)."New value: +"Optional rating for this viewing, in stars: 0.05 to 5 in steps of 0.05 (half stars, or a score out of ten divided by two)."
    • changedInput schema / properties / rating / minimum
      Previous value: -0.5New value: +0.05
    • removedInput schema / properties / rating / multipleOf
      Removed value: -0.5
  4. Changed5 schema fields changed
    • changedInput schema / properties / event_date / description
      Previous value: -"Date it happened, YYYY-MM-DD. Omit if unknown."New value: +"Date it happened: YYYY-MM-DD, or just YYYY-MM or YYYY when that is all the user knows. Omit if unknown."
    • addedInput schema / properties / item_id
      Added value: +{
      +  "description": "Library item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.",
      +  "type": "string"
      +}
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga"
      +]
    • changedInput schema / properties / title / description
      Previous value: -"The title (partial match supported)"New value: +"The title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)"
    • changedInput schema / required
      Previous value: -[
      -  "media_type",
      -  "title"
      -]New value: +[
      +  "media_type"
      +]
  5. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-destructive, non-idempotent write with openWorldHint false, so the description does not need to restate safety. It adds useful domain behavior beyond the annotations: these logged events feed history and stats and are distinct from the first-finish status path, though duplicate handling and auth requirements are not addressed.

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?

Three tight sentences lead with the action, follow with usage triggers, and then explain the key distinction from status tracking. The parenthetical user quotes are illustrative and earn their place, with no boilerplate or repetition.

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?

For a 7-parameter write tool with no output schema, the description covers purpose, usage triggers, and the downstream history/stats effect well enough to call it correctly. It does not say what the call returns or how duplicate logs are handled, which are meaningful but non-blocking gaps.

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?

With 100% schema description coverage across all 7 parameters, the schema already documents dates, ratings, item_id precedence, event_type defaults, and media types. The description adds no parameter-level detail beyond a passing mention of a date, so the baseline of 3 is appropriate.

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 opens with a specific verb ('Log') and resources ('completion', 're-watch/re-read/re-listen'), and adds the domain distinction that first finishes live in status while this tool records repeats for history and stats. There is a slight tension because the first sentence says it logs completions while the later sentence says first finishes are tracked by status, which could make an agent hesitate about first-time use.

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?

It gives an explicit trigger with natural-language examples ('watched Heat again last night', 'reread Dune') and points agents to the status mechanism when recording a first finish. It does not explicitly exclude bulk logging or repeated duplicate calls, but the primary when-to-use context is clear.

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