Skip to main content
Glama

Agentalog — Agent Auto Log

by com.agentalog
OverviewDiscussionsAdmin

Feed find

feed_find
Read-onlyIdempotent

Does this site publish a feed? Answers with every feed known for a domain — the question a reader or an agent actually asks. Find feeds by text, format, language and availability. Filter and text search run in the SAME full-text query: values inside one parameter are OR'd, different parameters are AND'd. Without q the order is by newest in the index (recent) and next_cursor is a keyset — follow next to walk everything. With q the order is relevance and paging is by offset. We index and link; the feeds belong to whoever publishes them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dominioYesDomain, with no scheme: example.com
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

B3/5.0
Behavior3/5

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

Annotations already cover read-only/idempotent/non-destructive safety. The description adds some operational context (results ordered by recency in the index, paging via keyset vs offset), but these mechanics reference query parameters that do not exist in the schema, so the disclosure is only partially useful. The closing note ('we index and link; the feeds belong to whoever publishes them') is a disclaimer rather than behavior.

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 purpose is front-loaded, but the paragraph spends most of its length on query/ordering/paging mechanics tied to nonexistent parameters and includes filler ('the question a reader or an agent actually asks'). Reasonably sized but not every sentence earns its place.

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

Completeness2/5

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

For a two-parameter, 100%-covered, no-output-schema tool, the description needs little more than scope plus the domain semantics. Instead it overreaches into a filter/paging model that does not exist in the tool, leaving the agent with an inaccurate mental model and no guidance on alternatives.

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

Parameters2/5

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

Schema coverage is 100% and both real parameters (dominio, retry_key) are documented in the schema, so the baseline would be 3. However, the description describes a set of filter/search parameters (q, text, format, language, availability, next_cursor, offset) that are entirely absent from the schema, which is actively misleading rather than merely redundant.

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?

States a clear verb+resource: finding every feed known for a domain, framed as answering whether a site publishes a feed. This domain-scoped discovery purpose is distinguishable from siblings like feed_search and feed_posts, though the name of an alternative is never used to sharpen the contrast.

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

Usage Guidelines3/5

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

Gives implied context ('the question a reader or an agent actually asks') and describes ordering behavior, but never states when to choose this over feed_search or feed_posts, nor any prerequisites or exclusions. Usage is inferable rather than guided.

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