Skip to main content
Glama

Check source freshness

check_source_freshness
Read-onlyIdempotent

Fetch one allowlisted official documentation page from the curated registry and compare its normalized text with the verified snapshot. Status is unchanged, updated, unavailable (could not be checked now) or unknown (no snapshot). Results are shared by all callers and cached for up to 15 minutes (1 minute when unavailable); live.cached and checked_at show when the page was actually fetched. When the per-source fetch limit is reached, status is unavailable with reason rate_limited. Publication and update dates are never inferred and are always null. Only registry source ids are accepted; no other URL can be requested.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source_id": "<source_id>"
    },
    "name": "check_source_freshness"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYesRegistry source id, as returned in search_guidance or get_guidance results.

Output Schema

NameRequiredDescriptionDefault
liveYes
statusYes
providerYes
snapshotYes
source_idYes
checked_atYes
provenanceYes
update_dateYes
canonical_urlYes
interpretationYes
publication_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source_id / enum
      Previous value: -[
      -  "claude-code-practices",
      -  "claude-code-library",
      -  "claude-code-index",
      -  "claude-platform-index",
      -  "claude-prompting",
      -  "codex-prompting",
      -  "openai-skill-authoring",
      -  "openai-plugin-package",
      -  "openai-plugin-skills",
      -  "openai-index",
      -  "openai-api-index",
      -  "codex-index",
      -  "openai-plugin-index",
      -  "openai-eval-skills",
      -  "oai-clear-context",
      -  "oai-reasoning",
      -  "oai-evaluation",
      -  "oai-structured",
      -  "oai-tools",
      -  "oai-untrusted-data",
      -  "oai-cache",
      -  "claude-sonnet-scope",
      -  "claude-progressive",
      -  "claude-tool-descriptions",
      -  "claude-evaluations",
      -  "claude-code-authoring",
      -  "claude-workflow-complexity",
      -  "agentskills-index",
      -  "agentskills-specification",
      -  "agentskills-optimizing-descriptions",
      -  "agentskills-evaluating-skills",
      -  "cursor-index",
      -  "cursor-prompting",
      -  "cursor-plan-mode",
      -  "cursor-models",
      -  "cursor-skills",
      -  "cursor-plugins-reference"
      -]New value: +[
      +  "claude-code-practices",
      +  "claude-code-library",
      +  "claude-code-index",
      +  "claude-platform-index",
      +  "claude-prompting",
      +  "codex-prompting",
      +  "openai-skill-authoring",
      +  "openai-plugin-package",
      +  "openai-plugin-skills",
      +  "openai-index",
      +  "openai-api-index",
      +  "codex-index",
      +  "openai-plugin-index",
      +  "openai-eval-skills",
      +  "oai-clear-context",
      +  "oai-reasoning",
      +  "oai-evaluation",
      +  "oai-structured",
      +  "oai-tools",
      +  "oai-untrusted-data",
      +  "oai-cache",
      +  "claude-sonnet-scope",
      +  "claude-progressive",
      +  "claude-tool-descriptions",
      +  "claude-evaluations",
      +  "claude-code-authoring",
      +  "claude-workflow-complexity",
      +  "agentskills-index",
      +  "agentskills-specification",
      +  "agentskills-optimizing-descriptions",
      +  "agentskills-evaluating-skills",
      +  "cursor-index",
      +  "cursor-prompting",
      +  "cursor-plan-mode",
      +  "cursor-models",
      +  "cursor-skills",
      +  "cursor-plugins-reference",
      +  "deepseek-thinking",
      +  "kimi-thinking",
      +  "gemini-prompting"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: shared cache with 15-minute TTL (1 minute when unavailable), live.cached/checked_at reflecting the actual fetch time, per-source rate limits surfacing as unavailable/rate_limited, and the guarantee that publication dates are never inferred. That is exactly the operational context an agent cannot get from readOnlyHint/idempotentHint.

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 core action and every sentence carries distinct information (statuses, caching, rate limits, null dates, id restriction). It is dense as a single unbroken block, so a reader must parse carefully, but there is no filler to cut.

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?

Even though an output schema exists, the description still defines each status value and the reason field, and it covers caching, sharing across callers, and rate-limit behavior. Nothing an agent needs to interpret or safely call this tool 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% and the enum already documents the accepted values, but the description adds real meaning: only registry ids work, no other URL can be requested, and ids originate from search_guidance or get_guidance. This prevents the common misuse of passing an arbitrary documentation URL.

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 chain (fetch + compare) and a specific resource (one allowlisted documentation page from the curated registry against its verified snapshot). The scope is narrow and unmistakable, and the reference to ids coming from search_guidance/get_guidance results implicitly separates it from those siblings.

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?

The constraints make correct usage clear: only registry source ids are accepted, no arbitrary URL can be requested, and rate-limited fetches return status unavailable. It does not explicitly say when to pick this over get_guidance or search_guidance, so alternatives are implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.