Skip to main content
Glama
PHUICMT

mcp-mt5

by PHUICMT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

snapshot_sources

Idempotent

Freeze source files into a timestamped folder under a destination to preserve an exact copy of their state at a given moment.

Instructions

Freeze a copy of source files into a timestamped folder under dest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
destYesAbsolute path to the folder that holds snapshots.
labelNoFolder name for this snapshot; defaults to a timestamp.
sourcesYesAbsolute paths of the source files to freeze.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / dest / description
      Added value: +"Absolute path to the folder that holds snapshots."
    • addedInput schema / properties / label / description
      Added value: +"Folder name for this snapshot; defaults to a timestamp."
    • addedInput schema / properties / sources / description
      Added value: +"Absolute paths of the source files to freeze."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "snapshot_sourcesDictOutput",
+  "type": "object"
+}
  2. First observedv0.4.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description does not contradict them. It adds the detail that the copy is placed in a timestamped folder under dest, which is useful context. However, it does not elaborate on what happens to the original files, whether the dest directory needs to exist, or any side effects beyond the copy.

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?

The description is a single sentence with no filler words. It front-loads the core action ('freeze a copy of source files') and specifies the destination location concisely. Every word contributes meaning.

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?

The tool is relatively simple, and the description covers the essential action. An output schema exists, so return values are presumably documented there. The description is sufficient for an agent to understand the tool's purpose, though it leaves minor questions like dest directory existence or label behavior to the schema, which is already thorough.

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?

The schema description coverage is 100%, with all three parameters (sources, dest, label) having descriptive texts. The description adds no extra parameter semantics beyond the schema, so a baseline score of 3 is appropriate given high schema coverage.

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?

The description uses a specific verb ('Freeze a copy of source files') and explicit resources, making it clear the tool creates a snapshot under a destination folder. It does not name an alternative sibling, but the verb 'snapshot' and the resource 'source files' clearly distinguish it from siblings like list_snapshots or compile, so purpose is clear.

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?

The description implies usage: when you want to freeze a copy of source files into a timestamped folder. However, it does not explicitly state when NOT to use this tool or mention alternative tools like list_snapshots or compile. The context is implied but not made explicit.

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

Deploy Server

Other Tools