Skip to main content
Glama
Sign In

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

by wiki.agenticweb
OverviewDiscussionsAdmin

stale

Read-onlyIdempotent

List standards whose last_verified date is older than N days (default 30, oldest first), optionally filtered by lifecycle step. Returns { threshold_days, count, records: [{ id, name, step, last_verified, days_since_verified }] }. Use stale to audit verification freshness; use changes to inspect actual specification edits since a date.

Input Schema

NameRequiredDescriptionDefault
daysNoreturn standards whose last_verified date is older than this many days (default 30)
stepNooptional lifecycle step filter (discover, identify, permit, read, act, coordinate, pay, present, account)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / days / description
      Added value: +"return standards whose last_verified date is older than this many days (default 30)"
    • addedInput schema / properties / step / description
      Added value: +"optional lifecycle step filter (discover, identify, permit, read, act, coordinate, pay, present, account)"
    • addedInput schema / properties / step / enum
      Added value: +[
+  "discover",
+  "identify",
+  "permit",
+  "read",
+  "act",
+  "coordinate",
+  "pay",
+  "present",
+  "account"
+]
    • removedInput schema / properties / step / maxLength
      Removed value: -40
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the default threshold of 30 days, the oldest-first ordering, and the exact return envelope. It does not mention result caps or pagination, which is a minor omission for a list tool.

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: selection rule first, return shape second, disambiguation third. Nothing is wasted, and the most decision-relevant information is front-loaded.

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, and the description compensates by spelling out the returned fields (threshold_days, count, records with id/name/step/last_verified/days_since_verified). Combined with the annotations and full schema coverage, an agent has everything needed to call and interpret this tool.

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%, and both parameters are documented in-schema including the enum values and the default of 30. The description largely restates 'older than N days' and 'optionally filtered by lifecycle step' without adding syntax or edge-case semantics, so the 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 ('List standards') plus the precise selection criterion (last_verified older than N days), default, and sort order (oldest first). It also names the sibling it is not ('changes'), so the agent can distinguish it 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?

Explicit routing: 'Use stale to audit verification freshness; use changes to inspect actual specification edits since a date.' This gives both the when-to-use and the competing alternative with the condition that selects between 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