Skip to main content
Glama
spranab

Saga MCP

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

activity_log

Read-onlyIdempotent

Review what changed and when using filters for action, entity, and time to track progress and recent updates.

Instructions

View the activity log showing what changed and when. Useful for understanding recent progress or reviewing what happened since the last session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sinceNoISO 8601 datetime - show only activity after this time
actionNoFilter by action type
entity_idNoFilter by specific entity
project_idNoScope to one project. Defaults to SAGA_PROJECT if set, else the whole database.
entity_typeNoFilter by entity type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.0
    • changedInput schema / properties / project_id / description
      Previous value: -"Scope to one project. Needed when a single database holds several projects; defaults to the SAGA_PROJECT env var if set, otherwise the whole database."New value: +"Scope to one project. Defaults to SAGA_PROJECT if set, else the whole database."
  2. Changed1 schema field changedv1.10.0
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "Scope to one project. Needed when a single database holds several projects; defaults to the SAGA_PROJECT env var if set, otherwise the whole database.",
+  "type": "integer"
+}
  3. First observedv1.5.3

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered and the bar is lower. The description adds the content contract ('what changed and when') and a temporal framing, but does not disclose ordering, pagination, or whether deleted entities appear in the log. There is no contradiction with the annotations.

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 with zero waste; the core statement is front-loaded and the usage guidance in the second sentence earns its place. Nothing is repeated from the schema or annotations.

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 simple read-only viewer with all-optional parameters, the description covers the core purpose and a realistic use case, while the schema documents the parameters and annotations cover the safety profile. Minor gaps remain — no response shape and no ordering semantics — but these are small for a log-viewing tool with no output schema.

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 83%, so the schema already documents five of six parameters, including the enums for action and entity_type and the SAGA_PROJECT default for project_id. The description adds little parameter-specific meaning — only a loose tie between session review and the 'since' parameter — so the high-coverage baseline of 3 applies.

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 states a specific verb ('View') and resource ('the activity log') with a clear content contract ('showing what changed and when'), which is unambiguous about the core function. However, it does not explicitly differentiate from siblings — the closest conceptual neighbor, tracker_session_diff, could plausibly overlap with 'reviewing what happened since the last session.'

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?

The second sentence gives explicit when-to-use context: 'understanding recent progress or reviewing what happened since the last session.' This is stated directly rather than merely implied, but there are no exclusions or named alternatives, leaving a small gap if an agent wonders whether tracker_session_diff serves the session-review use case instead.

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

Deploy Server

Other Tools