Skip to main content
Glama

stale_sources

Detect wiki drift by listing ingested sources whose original files changed and the pages still showing old versions, so you can re-import or refresh them.

Instructions

Lint the wiki for drift: sources whose original file changed after ingestion, with the pages that still reflect the old version. Re-import or refresh them in the app.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stale_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: "Lint" signals a read-only inspection, the output content is spelled out (sources plus affected pages), and "in the app" makes clear the repair happens outside this tool, which tells the agent not to look for a fixer tool. It stops short of saying whether the scan covers the whole wiki or how drift is determined.

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?

Two sentences, zero filler, and the core behavior is front-loaded before the remediation hint. Every clause contributes: what is checked, what is returned, and what to do about it.

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?

For a zero-parameter, annotation-free tool with no output schema, the definition covers the essentials by describing the return payload in prose. The only real gap is scope and drift-detection semantics, which an agent could reasonably wonder about before calling.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already conveys. The baseline for a parameterless tool 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?

The description names a specific operation (lint the wiki for drift) and defines the resource precisely: sources whose original file changed after ingestion, together with the pages that still show the old version. That is concrete enough to separate it from siblings like list_pages, recent_activity, and search_wiki without opening any schema.

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?

It implies the situation (checking whether ingested material has gone stale) and says what to do afterward, "Re-import or refresh them in the app." But it never states when to prefer this over recent_activity or search_wiki, and gives no preconditions or exclusions, so the when-to-use guidance remains inferred.

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