Skip to main content
Glama
Sign In

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

Listing dependencies

listing_dependencies
Read-onlyIdempotent

Read a tool's declared package/repository/domain chain and cached public source evidence. No purchase or collection. Repeated registry, repository, registration and DNS lookups, comparison code and an alert process that must keep running after the conversation. A declaration does not prove ownership. Source failures and missing dates remain unknown. Collected PyPI provenance is not independently verified. No measured token or money saving is claimed.

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>"
    },
    "name": "listing_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLive catalog listing ID.
api_passNoMAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.
retry_keyNoOptional retry key, up to 80 ASCII characters; same read for five minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, but the description adds useful caveats: declarations do not prove ownership, source failures and missing dates stay unknown, and PyPI provenance is not independently verified. The unexplained fragment about repeated lookups and an alert process is confusing, but it does not explicitly contradict the read-only annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the description then adds several caveats, a sentence about no token or money saving, and an ungrammatical fragment listing repeated lookups, comparison code, and an alert process. That fragment and the savings disclaimer do not help an agent select or invoke the tool, so the text is not efficiently structured.

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?

The definition is moderately complete for a read-only tool with rich annotations and a fully described schema, but with no output schema it does not explain the return shape or contents of the cached evidence. It also omits when-to-use guidance relative to closely related sibling tools.

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%, so the schema already documents id, api_pass, and retry_key. The description only refers generally to a tool's declared chain and cached evidence and does not add parameter-level meaning beyond that baseline.

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 names a specific read operation and resource: a tool's declared package/repository/domain chain plus cached public source evidence. It gives an agent a concrete object to fetch, but it does not explicitly distinguish this from siblings like get_listing or listing_security, and the fragment that follows weakens the initial clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not state when to use this tool rather than dependency_changes, watch_dependency_changes, listing_security, or get_listing. 'No purchase or collection' only rules out buying; it does not provide selection guidance or prerequisites.

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