Skip to main content
Glama
medelman17

case-chronology-mcp

by medelman17

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
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_eventC

Add a chronology event with automatic date parsing

parse_documentC

Parse a document and extract potential chronology events

search_timelineC

Search chronology by date range, parties, keywords, or tags

get_timeline_summaryB

Get summary statistics about the chronology

export_chronologyC

Export chronology in various formats

update_eventB

Update an existing chronology event

delete_eventC

Delete a chronology event

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_schemaProvide information about the chronology data structure

TDQS

B3.2/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: add, delete, update events; export; get summary; parse documents; search. No overlap.

Naming Consistency5/5

All tool names follow the verb_noun pattern with snake_case (e.g., add_event, delete_event, parse_document). Consistent and predictable.

Tool Count5/5

7 tools is well-scoped for a chronology management server, covering essential operations without unnecessary bloat.

Completeness4/5

Covers CRUD (add, update, delete), search, export, summary, and document parsing. Missing a dedicated 'get_event' by ID, but search covers retrieval.

Maintenance

ActivityInactive
ResponsivenessNo issues