Skip to main content
Glama

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

Feed post

feed_post
Read-onlyIdempotent

Read one post whole: the body in Markdown (content) and the author's formatting as safe HTML (content_html), plus the link to the original. ord comes from feed_posts; 0 is the newest. Two bodies for the same post, both from the copy we stored when we READ the feed — a request never fetches the site: content_html keeps the author's formatting through an allowlist (only known tags and attributes survive; script, style, iframe and event handlers are dropped with their content), and content is the same text as Markdown — the shape an agent usually wants. Neither can carry script. 404 when the feed or the position is unknown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFeed id, prefix fd_.
ordYesPosition of the post in the feed; 0 is the newest.
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.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: content comes from the stored copy, a request never fetches the site, the HTML is passed through an allowlist (script/style/iframe/event handlers dropped with contents), and neither body can carry script. That is exactly the sanitization and freshness behavior an agent needs.

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?

Front-loaded with the payoff (both bodies plus the link) before the sanitization detail. Slightly redundant — the allowlist sentence and the closing 'Neither can carry script' make the same point twice — but every sentence is load-bearing and readable.

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 carries the return-value burden, and it does: field names, formats, and the 404 error condition are all spelled out. Nothing needed to call this three-parameter read tool correctly is missing.

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 the schema already documents `id`, `ord`, and `retry_key`; the description's restatement that `ord` is 0-based-newest duplicates the schema. It adds no format or edge-case detail for `id` or `retry_key`, so baseline 3 applies.

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?

States a specific verb and resource ('Read one post whole') and immediately enumerates what comes back: Markdown body, safe-HTML body, and the original link. It also positions itself against the sibling feed_posts by explaining that `ord` originates there, so an agent can tell the two apart without opening schemas.

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?

Explicit workflow context: '`ord` comes from feed_posts; 0 is the newest,' and the failure mode '404 when the feed or the position is unknown.' It does not name when *not* to use this (e.g., vs feed_search for finding posts), so it stops short of full alternative routing.

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