SwiftKG MCP Server

Overview Schema Source Related Servers Discussions Admin

snapshot_list

List saved codebase metric snapshots in reverse chronological order, with optional branch filtering, to track changes in size, edges, and doc-comment coverage over time.

Instructions

List saved temporal snapshots of codebase metrics in reverse chronological order.

Each entry in the returned list contains a key (tree hash snapshot identifier), branch, timestamp, version, and a summary of key metrics (node count, edge count, doc-comment coverage) plus deltas vs. the previous snapshot. Use the key field when calling snapshot_show() or snapshot_diff(key_a=..., key_b=...).

Use this tool to answer questions like "how has the codebase grown?" or "when did doc-comment coverage improve?" or "show me only main-branch snapshots".

:param limit: Maximum number of snapshots to return (default 10; pass 0 for all). :param branch: If provided, filter to snapshots from this branch only (e.g. "main" or "develop"). :return: JSON array of snapshot metadata dicts, most recent first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`branch`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the list-only nature, the reverse-chronological ordering, the included summary fields, and the deltas-vs-previous behavior. It does not mention edge cases (e.g., empty list, invalid branch), but the core reading behavior is clear.

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?

Well-structured with an opening goal sentence, a result-detail paragraph, usage examples, and a param block. It is slightly long but every sentence adds distinct value; the only minor redundancy is restating 'codebase metrics' in the first and second sentences.

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?

For a read-only list tool with two params alert and no annotations, the description covers ordering, fields in each entry, deltas, defaults, the 0-means-all behavior, and how the key links to sibling tools. The presence of an output schema reduces the need to document the return shape beyond what is given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is effectively 0% since the input schema only gives names and defaults. The description compensates fully by explaining both parameters: limit caps results and accepts 0 for all, branch filters by branch with an example. This is exactly the semantic meaning the schema lacks.

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?

Clearest possible statement: 'List saved temporal snapshots of codebase metrics in reverse chronological order.' It names the operation, the resource, and the ordering, and it distinguishes the list view from snapshot_show/snapshot_diff by describing the summary-level content.

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?

Explicitly gives example questions this tool answers and tells the user to pass the returned 'key' to snapshot_show or snapshot_diff, which strongly signals boundaries against sibling tools. It does not explicitly say 'if you need full snapshot content, use snapshot_show instead,' so it falls just short of a perfect 5.

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