Skip to main content
Glama

Ingest status + what's new

wwdc_ingest_status
Read-onlyIdempotent

Displays the corpus version stamp, per-source ingest status, last-run metadata, and recent sessions so you can confirm which corpus is indexed and whether it is fresh before querying.

Instructions

Shows the corpus version stamp (ingest date, per-source status, session count), per-source last-run metadata, and the most recent sessions added. Use to confirm which corpus this is and that the index is fresh before querying.

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": "wwdc_ingest_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoISO timestamp; defaults to 7 days before the latest activity recorded in the index (state-derived, so repeated calls with unchanged state return identical output).
formatNoResponse formatmarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / since / description
      Previous value: -"ISO timestamp; defaults to 7 days ago."New value: +"ISO timestamp; defaults to 7 days before the latest activity recorded in the index (state-derived, so repeated calls with unchanged state return identical output)."
  2. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds useful context by listing what the response contains (version stamp, per-source status, recent sessions), which matters since there is no output schema. It does not mention the state-derived stability of results or any cost of the call.

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?

A single efficient sentence-front-loaded with what the tool returns and closing on the usage condition. The enumerated payload makes it dense but every clause carries information; no filler.

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?

With no output schema, the description must convey what comes back, and it does so concretely. The remaining gap is that two of three parameters (limit, format) are not addressed and no guidance is given on how large the 'recent sessions' window can be.

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 67%, so the schema partially documents parameters, but 'limit' has no description and only 'since' and 'format' carry schema text. The description adds nothing about limiting recent sessions or choosing a format, leaving parameter meaning entirely to the schema.

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 specific verb ('Shows') and enumerates the exact payload: corpus version stamp, per-source status, session count, last-run metadata, and recent sessions. It clearly distinguishes itself from query/search siblings like wwdc_search or wwdc_list_sessions, though it does not name a sibling explicitly.

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?

Gives a clear use case: confirm which corpus this is and that the index is fresh before querying. It does not state when to skip it or name the alternative for freshness checks, but the intended context is unambiguous.

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