Skip to main content
Glama
LNSHRIVAS

pysince-mcp

by LNSHRIVAS

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
stamp_file_readA

Call this immediately after reading a file for the first time. Must be called BEFORE check_staleness can detect changes to that file. Records current mtime and content hash.

check_stalenessA

Check whether a previously-stamped file has changed since you last read it. If no prior stamp exists it will tell you to stamp first. Call this before editing any file you stamped earlier — if stale, re-read it.

session_durationA

How long has this session been running and how many messages have been exchanged. Useful for understanding context age.

invalidate_sourceA

Manually mark all events from a source as stale. Used when you know a resource has changed and want to ensure stale warnings fire.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool serves a distinct purpose: stamping, checking staleness, invalidating sources, and querying session duration. No overlap in functionality.

Naming Consistency4/5

Uses snake_case consistently, but 'session_duration' is a noun phrase while others are verb phrases (check_staleness, invalidate_source, stamp_file_read). Minor inconsistency.

Tool Count5/5

Four tools is well-scoped for a file staleness tracker. Each tool covers a necessary operation without redundancy.

Completeness4/5

Core operations (stamp, check, invalidate) are present. Missing a tool to list all stamped files, but the essential workflow is covered.