Skip to main content
Glama
Sign In

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

Listing updates

listing_updates
Read-onlyIdempotent

Refresh up to 100 selected listings in one batch instead of opening each listing. The catalog stores the values seen at the last real change of a listing; counters and package versions change over time. After a search, use this batch or MCP listing_updates before comparing versions. These values may be cached for up to 15 minutes; generated_at is the slice generation date, not a check date for each record. Listings without a record are unknown and simply absent. GET /api/listings/:id already applies these values on top of the record.

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": {
      "ids": "<ids>"
    },
    "name": "listing_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesComma-separated listing IDs, at most 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important behavioral details: values may be cached for up to 15 minutes, `generated_at` is a slice generation date rather than a per-record check, and listings without records are absent rather than unknown. It also explains how `GET /api/listings/:id` relates to these values, which is useful operational context.

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 and most sentences add real value about staleness, caching, and absent records. However, the self-referential 'MCP listing_updates' phrase is awkward, and the description could be tightened slightly for a one-parameter tool.

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 batch tool with full schema coverage and annotations, the description provides enough to call it correctly and interpret freshness and missing records. It does not explicitly describe the return shape, but the absence of an output schema makes that a minor gap.

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%, and the single `ids` parameter is already documented as comma-separated listing IDs with a maximum of 100. The description only repeats the batch size limit ('up to 100 selected listings') and adds no new syntax or format details, so the baseline 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 first sentence gives a clear verb ('Refresh'), resource ('listings'), scope ('up to 100 selected'), and batching contrast ('instead of opening each listing'). It distinguishes the tool from per-listing retrieval, but does not explicitly name the sibling tools it replaces and includes a confusing self-reference to 'MCP listing_updates'.

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 clearly says to use this after a search and before comparing versions, which gives the agent a specific usage context. It does not state when not to use it, and the phrase 'this batch or MCP listing_updates' is redundant and slightly muddies the guidance.

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