Skip to main content
Glama
Sign In

Agentic Web Wiki — standards reference, probe, validate, template

by wiki.agenticweb
OverviewDiscussionsAdmin

digest

Read-onlyIdempotent

Fetch the curated daily agentic-web news and adoption digest for a YYYY-MM-DD date (defaults to latest). Returns { date, headline, highlights, new_instances, spec_changes, stats }; pass list: true to return available dates only, or compact: true (alias: include_stats: false) to omit the census stats block. Use digest for daily narrative summaries; use changes for raw field-level diffs.

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD or latest
listNotrue: list published dates
compactNotrue: omit stats block
include_statsNofalse: omit stats block

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / compact / description
      Previous value: -"true: omit the 35 KB stats block and return only digest metadata and news items"New value: +"true: omit stats block"
    • changedInput schema / properties / date / description
      Previous value: -"YYYY-MM-DD or latest (default)"New value: +"YYYY-MM-DD or latest"
    • changedInput schema / properties / include_stats / description
      Previous value: -"false: omit the stats block"New value: +"false: omit stats block"
    • changedInput schema / properties / list / description
      Previous value: -"true: the index of published dates instead of one digest"New value: +"true: list published dates"
  2. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
+  "description": "true: omit the 35 KB stats block and return only digest metadata and news items",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_stats
      Added value: +{
+  "description": "false: omit the stats block",
+  "type": "boolean"
+}
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: the default-to-latest fallback, the exact return shape keys, and the mode toggles. It stops short of describing pagination, size limits, or what happens for an unpublished date, which keeps it off a 5.

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

Conciseness5/5

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

Three dense sentences, purpose first, then return shape, then modes, then sibling routing. No filler or restated name/title; every clause carries operational information.

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?

No output schema exists, and the description compensates by enumerating the return keys { date, headline, highlights, new_instances, spec_changes, stats }. Defaults, alternate modes, and sibling routing are all covered; only edge-case behavior (unknown date, empty digest) is unaddressed.

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 description coverage is 100%, so the baseline is 3. The description earns above baseline by documenting the alias relationship (compact is an alias for include_stats: false) and the default-latest semantics of `date`, neither of which the bare schema fields spell out.

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 ("Fetch the curated daily agentic-web news and adoption digest") plus the date keying and default-latest behavior. It also explicitly distinguishes itself from the sibling tool `changes`, so an agent can choose between them without opening either 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?

Gives an explicit routing rule: "Use digest for daily narrative summaries; use changes for raw field-level diffs." It also states the two alternate modes (list: true for dates, compact: true to omit stats) with the conditions that select them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agentic Web Wiki — standards reference, probe, validate, template 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