Skip to main content
Glama
Sign In

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

Watch dependency changes

watch_dependency_changes

Use an existing paid watch pass to follow package, publisher, repository and domain changes. Never purchases a pass. The listing must already be in your watchlist. No separate purchase. Sources refresh every six hours through shared caches. Source quotas can defer a check. History records before, after, source and observation date. Domain expiry alerts use 30, 15 and 7 days when the registry publishes a date. Missing dates and source failures remain unverified. Account holders receive operational e-mail; wallet owners read API history. No account-recovery or takeover attempt is made.

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": {
      "id": "<id>",
      "enabled": "<enabled>"
    },
    "name": "watch_dependency_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLive catalog listing ID.
enabledYesExplicit requested state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real context beyond the annotations: six-hour refresh via shared caches, quota-based deferral, history fields (before, after, source, observation date), 30/15/7-day expiry alert thresholds, and unverified status on source failure. Against that, several sentences ('No account-recovery or takeover attempt is made', e-mail vs API delivery channels) read as boilerplate rather than operational guidance, and the effect of setting enabled=false is never described.

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?

The purpose is front-loaded in the first two sentences and the sentences are short and scannable. Some of the trailing content (account-recovery disclaimer, wallet-versus-account delivery channels) does not help an agent decide or invoke, so the list is slightly longer than it needs to be.

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?

For a two-parameter toggle with no output schema, the description covers cadence, quota risk, history contents and alert thresholds well. The critical gap is the meaning of the enabled flag as a state transition and what the caller gets back, leaving an agent unable to predict the effect of the call.

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 'id' (live catalog listing ID) and 'enabled' (explicit requested state) are already documented. The description adds nothing about either parameter, in particular never clarifying whether enabled=false disables an existing watch or merely records an unfulfilled request.

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 first sentence gives a specific verb and resource ('follow package, publisher, repository and domain changes') plus the mechanism ('existing paid watch pass'), which distinguishes it from a purchase flow. It does not, however, distinguish this from the sibling watch_tool or explain that the tool is toggling a watch state via the 'enabled' flag.

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?

Clear preconditions are stated: a pass must already exist, the listing must already be in the watchlist, and no purchase occurs. What is missing is routing to alternatives (watch_tool to add, unwatch_tool to remove, dependency_changes to inspect results) so an agent knows when to pick this over those siblings.

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

All Agentalog — Agent Auto Log toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources