everlog-mcp

Overview Schema Source Related Servers Discussions Admin

journal_stats

Read-onlyIdempotent

Calculate writing statistics for entries and total words by year or month, with optional journal and date-range filters.

Instructions

Writing statistics: entries and total words per year (or month, 'YYYY-MM'), plus totals. Optionally restricted to one journal and/or an inclusive YYYY-MM-DD date range.

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

Input Schema

Name	Required	Default
`journal`	No
`end_date`	No
`group_by`	No	year
`start_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that the report is composed of entry counts and total word counts at year/month granularity plus overall totals, which is mild extra context; it says nothing further about computation cost, empty-result behavior, or scope defaults.

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?

Two sentences, front-loaded with the tool's output, followed by the optional filters. No filler or redundant restatement of the name.

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?

Rich annotations and an output schema mean the description needn't explain return structure or safety, and it covers scope, filtering, and aggregation granularity for this simple 4-parameter tool. The remaining gap is unspecified default behavior when no journal or dates are supplied.

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

Parameters4/5

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

With 0% schema description coverage the description must carry the parameter burden, and it largely does: it explains the journal restriction, the inclusive nature of the start/end date range with the YYYY-MM-DD format, and the year-vs-month grouping including the 'YYYY-MM' label shape. It does not map each filter to its parameter name or mention that grouping defaults to year, so it falls short of a perfect 5.

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?

"Writing statistics: entries and total words per year (or month...), plus totals" states a specific computed resource and the granularity of the aggregate. It implicitly separates itself from retrieval siblings like search_entries or list_journals by being an aggregation tool, though it never names or contrasts them explicitly.

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 notes that results can be narrowed to one journal and/or a date range, which implies the useful calling contexts, but it never states when to prefer this over sibling listing/search tools or what happens when all filters are omitted (all journals, all time).

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

Deploy Server