Skip to main content
Glama

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

Feed posts

feed_posts
Read-onlyIdempotent

What has this feed published? The posts of one feed as our queue read them — title, date, author, summary, categories and enclosure, without the body. Find the feed first (feed_find or feed_search); this takes an id from this index, never a URL. Up to 40 posts, in the order the feed publishes them, WITHOUT the body — the body of one post comes from /items/:ord. It is OUR copy, read on our own schedule — not the live feed and not a proxy: the only thing this endpoint accepts is an id from this index, never a URL. read_at says when we read it. Empty list when the feed has not been read yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFeed id, prefix fd_.
retry_keyNoOptional retry key, up to 80 ASCII characters; same read for five minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / api_pass
      Removed value: -{
-  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • addedInput schema / properties / api_pass
      Added value: +{
+  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
+  "type": "string"
+}
    • addedInput schema / properties / retry_key
      Added value: +{
+  "description": "Optional retry key, up to 80 ASCII characters; same read for five minutes.",
+  "type": "string"
+}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the read-only idempotent safety profile, and the description still adds substantial behavior: it is a cached copy read on our own schedule rather than live data, capped at 40 posts in publish order, excludes the body, and includes read_at as the read timestamp. This is the kind of context annotations cannot express.

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

Conciseness3/5

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

The opening is strong and front-loaded, but the description repeats itself: 'never a URL' appears twice, 'WITHOUT the body' twice, and the 'our copy / not the live feed' idea is stated in two overlapping sentences. Trimming the repetition would preserve all the signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe returns, and it does: the fields returned, the 40-item cap, ordering, the read_at timestamp, and the empty-list case. Nothing an agent needs to call and interpret this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds a genuine constraint beyond the schema: the id must come from this index and never be a URL, which tells the agent how to source the value. It adds nothing for retry_key's semantics beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('posts of one feed') plus the scope ('as our queue read them') and enumerates the returned fields. It clearly separates itself from feed_post (single body) and feed_find/feed_search (resolution), so an agent can pick it without opening the schema.

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

Usage Guidelines5/5

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

Explicit routing: 'Find the feed first (feed_find or feed_search)' and an explicit precondition that it 'takes an id from this index, never a URL.' It further states when-not: it is not the live feed and not a proxy, and returns an empty list when the feed has not been read. Alternatives and exclusions are both named.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources